implement-spec
You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.
The spec and tickets are GitHub issues. Use the gh CLI, which infers the repository from the clone:
- Read a ticket:
gh issue view <number> --json number,title,body,labels,comments - Close a ticket:
gh issue close <number> --comment "<what landed>"
Before starting, read GLOSSARY.md at the repo root (or GLOSSARY-MAP.md and the per-context glossaries it points at) and any ADRs under docs/adr/ or src/*/docs/adr/ that touch the area. If they don't exist, proceed silently. Use their vocabulary in branches, commits, and PRs, and surface any ADR conflict rather than silently overriding it.
The goal is the entire spec implemented on a single integration branch, with every ticket resolved the way GitHub closes work: a merged PR with a closing reference, or a direct gh issue close.
The tickets are not a list of steps. They are a task graph with blocking relationships between them. This means there is always a frontier of tickets which are ready to be grabbed.
Communication to and from subagents should be sparse. Communicate primarily through context pointers: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.
Implementer subagents should be run in the background where possible for maximum concurrency.