write-planlisted

# Planning Phase You are entering the **Planning Phase** of the Structured Agentic Development Workflow. > **Output style:** Check memory for `workflow-config:caveman-level`. If set, adapt your output brevity to that level while preserving technical accuracy. ## Your Mission Write a detailed, phased implementation plan for: **$ARGUMENTS** ## Rules 1. **Do NOT write implementation code.** You are producing a plan document, not building the feature. 2. **Save the plan to `docs/plans/new/<feature-name>.md`** — not to `docs/plans/` (that is for active plans only). 3. **Divide the work into isolated Phases.** Each phase should be independently testable and reviewable. 4. **Be hyper-granular.** Write the plan so that a different agent — possibly a smaller, faster model — can execute it without ambiguity. Name specific files, functions, classes, and test cases. 5. **Include test criteria for each phase**, expressed as the **exact command + expected output** — not a vague "tests pass". The executing model needs an objective stop condition, not a judgment call. - **Operational claims need a number and a way to measure it.** "Fast", "scales", "low memory", "won't block the UI" are not criteria — a build model cannot implement them and a reviewer cannot falsify them. Give a threshold and name the command or harness that measures it, or cut the claim from the plan. - **Never write a credential into a command.** The plan is committed to the repo and read by every downstream mo