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. Every phase-boundary stop stays in the main conversation. 1. Get the scratch directory using `!scratch-dir.sh`. The stack is in the injected `<repo-context>` block. Persist the task's verbatim source as follows: - If a matching brief already exists (check with `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`. Exception: if `$ARGUMENTS` points to a file, reference it instead. - This file is the durable source of truth for anything the task provides verbatim; conversation context may be compacted, but this file persists. - If `$ARGUMENTS` is empty because the task was only stated in prior conversation, write the fullest available verbatim restatement and note 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