implement-spec
Implement the spec
Complete the supplied spec on one integration branch. Read tickets as a dependency graph: a ticket is ready when its blockers have landed and it has no active worker.
Read AGENTS.md and CLAUDE.md for the configured agent root and {agentRoot}/issue-tracker.md for ticket location and completion rules. Use setup-skills only if missing configuration prevents work; a supplied local spec and ticket directory can provide enough information to proceed.
Before applying a skill below, load it through the Skill tool when available; otherwise read its SKILL.md. Use internal subagent tools for workers, not user-owned chats. If delegation is unavailable, work through the same graph sequentially and state the limitation.
Establish the graph and integration branch
- Read the spec, every associated ticket, repository guidance, and the relevant glossary and ADRs. Record the baseline commit and ticket dependencies. Resolve missing blockers and cycles before dispatching their dependent work.
- Inspect the checkout and attached worktrees. Preserve unrelated changes. Create or reuse a suitable integration branch from the agreed baseline, following the repository's branch convention. Never reset a dirty checkout to make its base match.
- Agree testing seams from the spec or discussion before workers start. Give each ticket acceptance criteria, its validation commands, and ownership of shared fixtures or generated contracts. For generated files, identify authoritative inputs, the generation command, and the project's required generation order. Workers escalate a material change to these seams instead of independently renegotiating the whole plan.
- Dispatch independent ready tickets up to available agent slots. Keep capacity for coordination and review. Serialize tickets that repeatedly edit the same files or share an unsettled contract even if the written graph omits that dependency.
Exploration is optional. When repeated investigation would otherwise slow workers, delegate a bounded question and save cited notes under {agentRoot}/research/ or a shared temporary directory. Give later workers pointers rather than copies.