implementlisted

# Implement Turn one plan task into shipped code through small, well-described commits — nothing more than the task asks for, nothing left messier than it was found. ## When to use When the workflow reaches the `implementation` capability for a task in `plans/*.md` that is not yet checked off, or when the group chat routes work to the developer persona. ## Method 1. **Re-read the task's contract first.** Open the linked spec section and the plan task's acceptance criteria before writing any code. If a test already exists for this task (unit/integration/e2e), run it — it should fail (**red**). If no test exists, note that in the report; do not silently skip testing, escalate to the `testing` capability if the task needs one. 2. **Build the smallest change that satisfies the criteria (YAGNI).** You Aren't Gonna Need It: implement only what the current task requires — no speculative config, no unused abstraction, no extra endpoint "while we're in here". Extra scope is a separate task, not a freebie. 3. **Make it pass, then clean it up (green → refactor).** Get the existing/linked test green with the simplest correct code, then refactor for clarity and to remove duplication (DRY — Don't Repeat Yourself: extract only when a *third* real occurrence appears, not on the first hint of similarity). 4. **Apply the boy-scout rule to code you touch.** Leave the lines you had to open cleaner than you found them (naming, dead code, obvious lint issues) — but do no