Implement a spec

Implement the entire spec on one integration branch, treating its tickets as a dependency graph. One coordinator owns merges, canonical project artifacts, and tracker updates.

1. Read the full spec, tickets, blocking edges, existing branch state, and configured tracker. Reuse the current source of truth. If no tracker is configured, tell the user to run /setup-matt-pocock-skills; until then, local artifacts can carry the graph without external publication. Invoke /domain-modeling to resolve project docs and /principles for implementation before code changes. Complete when scope, accepted seams, branch base, ready frontier, and any declared migration verification units are explicit and the graph has no unresolved cycle.
2. Create or reuse an owned integration branch. When the tracker closes work through PRs or the user asks for one, and publication is authorized, open a draft PR marked as closing the spec and tickets after the first merge in step 3. Gather bounded shared exploration once when useful, saving its notes outside the repository where every writer can read them. Each ready ticket runs through /pstack-mode's playbook that fits on two terms: the ticket's accepted design is /architect's chosen shape, so no second design round runs, and the playbook stops at a verified commit on the ticket's branch, since step 4's single /review-loop and step 5's PR replace its Opening a PR. Invoke /swarm to dispatch ready tickets within host capacity, each to a fresh writer on its own worktree based on the verified integration revision. In T3 Code the writer is a T3 child task on /swarm's T3 route whose brief says to follow the installed pstack-mode SKILL.md on those terms, since a native subagent can't run a playbook that spawns subagents of its own; elsewhere, run each ticket's playbook from this chat and delegate its writer step through /swarm. Point writers to the spec, tickets, notes, and commits instead of duplicating them, and explicitly delegate /tdd, /principles for implementation, resolved principle instructions, accepted design decisions, and acceptance criteria. Each writer merges the integration tip into its branch before reporting done. Inspect a wrong worktree base and preserve its changes before repair; never reset unknown work. Complete when every running ticket has an owner, base, playbook, applicable principle owners, and evidence contract.
3. Inspect each terminal result, merge accepted changes serially, and update the frontier only after the declared ticket or migration-phase checks pass. For a coupled migration, use /principle-migrate-callers-then-delete-legacy-apis for the unit's completion and dependent-work gates. Writers return proposed domain edits; reconcile them through /domain-modeling before canonical docs change. Use the existing tracker graph and link execution evidence instead of duplicating tickets. Complete each ticket only at its declared verification boundary with its integrated acceptance evidence.
4. When all required tickets are integrated, recheck /principles for verification, run relevant whole-spec checks, and invoke /review-loop once at the final revision, passing it any review evidence that covers this exact artifact. After its fixes, recheck affected whole-spec behavior. Complete when the entire spec is demonstrated against the actual artifact or the validated subset and remaining blockers are explicit.
5. Deliver a draft PR by default when authorized, using /pr and reusing one opened in step 2. Keep readiness, ticket closure, and merging at their explicitly authorized project boundaries; code on an unmerged branch is not automatically shipped. Use native worktree archive/removal for owned managed checkouts after inspecting preservation needs. Complete when all workers are accounted for, evidence survives, and no unknown work is removed.