build

Lead build phase. Goal: Take a fully specified GitHub issue and produce working code. Builds a feature using TDD. Produces implementation code in a worktree. Hands off via the worktree for review.

I/O

• Input: A GitHub issue number (with architecture/design decisions) and any additional resources.
• Output: A feature branch in a worktree with all acceptance criteria implemented, tests passing, and clean incremental commits. Ready for review.

Scope Assessment

Divide the issue into work units (sub-issues or file groups) which can be worked on in parallel by multiple build workers. Consider complexity, collision avoidance, dependencies, and risk when defining work units.

See ${CLAUDE_PLUGIN_ROOT}/_shared/composition.md for spawn cost models.

Process

Read references/process.md for step-by-step process, TDD, context hygiene, and commit rules.

1. Run pre-flight (repo/scope confirmation).
2. Read the issue and linked sub-issues.
3. Create worktree, init ./.claude/NOTES.md with task list.
4. Invoke Skill("scope-assessment") with work units derived from sub-issues and file groups → receive agent plan: spawn parallel Agent("agents/workflow-build-worker.md") — one per work unit.
5. Consider invoking Skill("compaction-protocol") for context management during long build sessions.

Output

Branch: <branch>
Worktree: <path>
Status: All AC implemented, tests passing

Rules

• Always create a worktree with wt switch --create <branch> before writing any code. Never code in the main repo directory.
• TDD: Write tests before implementation code.
• Context Hygiene: Keep NOTES.md updated with progress; use compaction when context limits are reached.