todou-planlisted

# todou plan Produce the implementation plan for a card as a **spec set on the issue**, and drive it through todou's spec review loop (inline annotations + approve/request-changes verdicts) until approved. This replaces the old specs/-directory + external-review flow: git never carries the documents, the tracker does. Read `/todou-cli` first; `<proj>` comes from the host project's config. ## The spec set Work in a scratch directory (temp dir or an untracked path — these files are **never committed to git**): - `proposal.md` — the user's original requirements, **excluding anything already recorded on the tracker**: the issue body, comments, and question answers live in the timeline and are referenced (`#N`, permalinks), never copied. What belongs here verbatim is only what has no tracker trace — requirements the user stated in the terminal/chat, decisions from outside channels — recorded like a transcript, with no judgment added. If a brainstorm preceded this (see /todou-brainstorm), start from its proposal.md. - `design.md` — the system/architecture design in brief. Note any third-party library you introduce or well-known algorithm you hand-implement. If a brainstorm produced a validated design, carry it over. - `api.md` — only when API design is involved: the endpoints/schemas. - `plan.md` — the detailed executable plan. This is the deliverable the implementer follows; concrete steps, file-level where it helps, with verification baked in. **Keep proposal.m