flow-planlisted

## Prerequisites - The task is stated clearly. If $ARGUMENTS is vague, ask one focused clarifying question before anything else. ## Procedure Steps 1-4 are the grounding phase; steps 5-10 are the planning phase. Keep this context lean: delegate broad code exploration and check-running to the scout or checker agent, but every phase-boundary stop stays in the main conversation. 1. Get the scratch directory: `!`scratch-dir.sh``. Stack is in the injected `<repo-context>` block. Persist the task's verbatim source: if a matching brief already exists (`ls -t "$(scratch-dir.sh)"/brief-\*.md "$(scratch-dir.sh)"/feature-\*.md 2>/dev/null | head -1`), read it. Otherwise write $ARGUMENTS byte-for-byte, including any embedded code, scripts, or replacement text blocks, to `$(scratch-dir.sh)/brief-<slug>-<YYYYMMDD-HHMM>.md` - this file is the durable source of truth for anything the task gives verbatim; conversation context can compact away, this file cannot. If $ARGUMENTS is empty because the task was only stated in prior conversation, write the fullest verbatim restatement available and say plainly in the file that it is a reconstruction, not the original. Print the brief path. 2. Ground in the project. Read `CLAUDE.md` at the project root in full, plus any `CLAUDE.md` on the path to the target area. Read the README only if its headings explicitly cover the task area. Check `git status` and `git log -5 --oneline`; note uncommitted work and recent direction. Identify the CI checks the