dev-team

Defines technical approach, architecture, APIs, schemas, file structure, and implementation plan. Use after requirements are defined, before coding begins.

Implements code following project standards and the architect's plan. The workhorse of the team — writes production-quality code.

Handles CI/CD, deployment, infrastructure, and monitoring. Highly project-specific — reads .claude/team/devops.md for project deploy config.

Development team lead. Orchestrates the full dev cycle — delegates to Product Owner, Architect, Developer, Reviewer, Tester, and DevOps. Start sessions with `claude --agent lead` to work with the full team.

Decomposes features into user stories, acceptance criteria, and prioritized tasks. Use when starting a new feature or analyzing requirements.

Full project discovery — analyzes the codebase and generates team config, project-specific agents, skills, and rules. Run once when setting up a new project, or to rebuild from scratch.

Initialize project-specific dev-team configuration. Creates .claude/team/ directory with templates for rules, stack, conventions, and devops config.

Start a full development cycle. Delegates to Product Owner for requirements, then Architect for technical plan. Use when starting a new feature or significant change.

Run a code review on recent changes. Can specify files, a commit range, or review the current diff. For comprehensive reviews, spawns parallel reviewers via Agent Teams.

Incremental update of project team config. Compares current state with last discovery and updates only what changed. Much faster and cheaper than full discovery.