implement-speclisted

This is the loop `/ask-matt` describes after `/to-tickets`: `/implement` per ticket in a fresh context, then the next. You stand in for the human running it. A spec arrives as tickets with blocking edges. The **frontier** is the open `ready-for-agent` tickets whose blockers are all closed; the **next ticket** is the lowest-numbered one. Each ticket gets a **round** at a time: a **subagent** of your own harness, in the ticket's own worktree. A finished branch clears a **gate** before it **lands**. After every landing you pick the next ticket. One round at a time, one spec per land base at a time. You chart, gate, and land. The agents implement, review, adjudicate, and answer review. `ready-for-human` tickets stay on the chart until the human closes them. The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`. `docs/agents/issue-tracker.md` holds the forms for sub-issues and blocking edges. [`ROUNDS.md`](ROUNDS.md) is how a round is spawned, pinned to its worktree, continued, and read; read it before the first round. The **chart** is your record of the spec on disk, a filled copy of [`CHART.md`](CHART.md) at `worktrees/agent-logs/spec-<id>-chart.md`, where `<id>` is the spec issue number or the file stem of a local spec. When a ticket's land base isn't the default branch, read [`LAND-BASE.md`](LAND-BASE.md). ## Start Fetch and fast-forward the primary checkout onto the land base before anything