implementlisted

Implement the plan at `docs/specs/<YY_MM_DD_HH>_<name>/plan.md`. ## Plan Discovery **With `$ARGUMENTS`:** resolve against `docs/specs/` — look for `docs/specs/<YY_MM_DD_HH>_<name>/plan.md` using the full dated spec identifier. **Without `$ARGUMENTS`:** 1. List all `*/plan.md` files under `docs/specs/` 2. Extract the `YY_MM_DD_HH` prefix from each folder 3. Use the file with the latest timestamp prefix ## Orchestration Read the plan file first. Then decide based on plan size: - **1–2 steps or trivial changes:** implement inline (no sub-agent needed) - **3+ steps, or steps spanning distinct areas of the codebase:** spawn a **developer sub-agent** per major phase When spawning a developer sub-agent, brief it with: - The full plan text - Which step(s) it is responsible for - Relevant project rules (`CLAUDE.md`, any project rules directory) — code style and any domain-specific conventions - Current file state / context it needs (read key files first and include excerpts) - Whether any external tool the plan depends on (an editor, engine, or service with its own connection state) is available and connected - For steps touching source code: write the test for the new behavior first so it fails against the current code, then implement until it passes — never disable or weaken an existing test to force a pass, fix the underlying code instead After each sub-agent phase: 1. Relay its results and any errors to the user 2. Verify the work (check for errors, read changed files) bef