implement-spec

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

Resolve the issue tracker the way /to-tickets does: an explicit user instruction, else docs/agents/issue-tracker.md (written by /setup-skills), else local markdown under .scratch/<feature-slug>/tickets/.

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.

Models and effort

Every ticket has a > **Difficulty:** line. Each implementer subagent runs on the model that line suggests for the current host, at a pinned effort.