implement-spec

You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.

The issue tracker should have been provided to you. If not, read the target repo's instructions (AGENTS.md, AGENTS.local.md, docs/agents/issue-tracker.md); when none names a tracker, ask the user which to use.

The goal is the entire spec implemented on a single integration branch, with every ticket resolved the way the issue tracker closes work.

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.

Gates

These are the same gates /implement holds for one ticket, held here for the whole spec. A failed gate blocks every step after it.