C9PG
Claude Code Docs

Adoption Roadmap

The fastest way to create resistance is to roll out every Claude Code feature at once. The better pattern is staged adoption.

Layer 1: Foundation

When: Day 1

  • use the team account
  • complete First-Time Setup
  • write a short CLAUDE.md
  • teach /plan, /context, /compact, and /rename

Layer 2: Daily Flow

When: Week 1

Layer 3: Shared Baseline

When: Week 2

  • commit shared settings only after the team understands the workflow they are encoding
  • add one shared skill that captures a proven pattern
  • add one small hook only when it removes repeated pain or risk

Layer 4: Team Rollout

When: Week 3+

  • standardize only the rules the team is ready to live with
  • review plugins through /plugin
  • use Team Leader Setup to decide what to enforce now versus later

Layer 5: Scale

When: Later

  • use /batch for truly parallel migrations
  • add subagents, stronger hooks, or CI/CD automation only when the repo has earned that complexity
  • move into Scaling Workflows and CI/CD Integration when the basics are stable

Layer 6: Continuous improvement

When: Ongoing

  • review release notes regularly
  • keep shared setup small enough to maintain
  • turn proven team habits into skills, rules, and hooks instead of inventing them in advance