implementlisted

Execute a plan, spec, or in-conversation agreement by dispatching a fresh subagent per task, reviewing each task before the next begins. The main model orchestrates; it does not write code. ## Input Start from a plan file, a spec, or whatever was agreed in conversation. First action: turn it into a task list — one entry per independent unit of work. If the input is too vague or coupled to break into tasks, say so and suggest `write-plan` first. ## Orchestrator stance Per task, build a self-contained brief and dispatch it to a fresh subagent — the brief template is in [references/briefing.md](references/briefing.md). A fresh subagent has no memory of prior tasks or this conversation, so the brief carries everything it needs: objective, files, interfaces from earlier tasks, verification commands, and boundaries. Never implement the task directly, even for a change that looks trivial — the point is that every line of code passes through an implementer-then-reviewer gate. ## Per-task loop 1. Dispatch an implementer subagent with the task brief. It implements, tests, and commits, then reports back. 2. Dispatch a reviewer subagent against the resulting diff. It checks two things: spec compliance (does the diff match the brief, nothing missing, nothing extra) and code quality. 3. If the reviewer raises critical or important findings, dispatch a fix subagent with the findings, then re-review. Repeat until clean. 4. Mark the task complete and move to the next one. ## Model sele