Deliver the spec and its dependency-aware ticket graph on one integration branch. Create one change request or review equivalent when the workflow requires it or the user requests it. For explicitly configured or requested branch-only delivery, report the integration branch and review record. Ticket and parent-spec closure still follow their configured acceptance events. Use pr when creating the change request. The coordinator owns phase transitions; code-cleanup returns validation evidence and code-review returns findings.

Read the spec, all tickets, docs/agents/issue-tracker.md, docs/agents/code-host.md, and docs/agents/workflow.md, or reuse their unchanged contents from context. The tracker configuration defines work item types, routing, and relationships. The code-host configuration defines branch and change-request operations. In repos configured before code-host.md existed, use any code-host operations already recorded in issue-tracker.md until setup is refreshed. The workflow defines checks, finding dispositions, and ticket/spec closure points. Deliver the accepted outcomes and necessary work in scope; leave optional improvements out unless the user accepts them or they block delivery. If configuration is missing, inspect existing contribution rules and CI, preserve the user's authorized scope, and clarify only decisions needed to proceed. Recommend /setup-snappedly-skills when repository-wide configuration is needed.

Select scope and ownership

Invoking implement-spec chooses whole-spec delivery, not a fixed testing or agent count. Assess the integrated change first. For a small, low-risk spec, implement its tickets in the current agent, use focused verification and local cleanup, review the integrated diff locally, and deliver the configured review outcome. Use the independent review phases below only for substantial cross-module work, security or data-integrity risk, or explicit user/repository requirements.

Assign each check and review once. Workers, including workers using implement, perform ticket or fix implementation, focused checks, local cleanup, and a self-check of their diff. The coordinator owns integrated checks, review selection, finding disposition, and delivery. State this boundary in each brief. Worker completion returns to the coordinator; it does not start another review or orchestration chain.

The coordinator also owns the configured delivery and closure transitions. At each relevant event, perform due actions assigned to the agent within the requested scope and verify their resulting state. Reuse applicable recorded sign-off. Keep transitions awaiting another event or actor pending, with the required evidence and responsible actor recorded. Ticket completion and parent-spec acceptance are separate decisions; workers return evidence rather than closing work independently.

TDD applies to changed logic according to its scope guidance. Presentation-only tickets use visual verification even inside a large spec. Required integrated checks still cover interactions across tickets.

For multi-slice work, check that tickets relying on the tracer bullet's unverified path or contract have a blocking edge to it. Add any missing edge to the run graph and tracker before dispatch, then recompute readiness. Integrate and verify the tracer bullet against its acceptance criteria before releasing dependents. Continue when the result supports the plan; pause only when it reveals a material change to the agreed outcome, contract, or scope.

Budget and delegation

Before launching agents, state a short budget: implementation assignments, optional exploration, initial applicable review axes, at most one fix assignment, follow-up axes, and expected full validation passes. Derive counts from independent work and risk, rather than UI file or ticket count. Small related tickets normally use no agents; substantial independent tickets may use workers and the required review axes. Cleanup and conflict-free integration stay with the coordinator. Plan one integrated validation pass with the applicable checks; reserve a fix assignment or follow-up reviewers only when needed.