planlisted

# /mneme:plan — Turn a task in words into a reviewed delta-spec The ENTRY of the pipeline. It takes a task described in plain words, scouts the code and prior memory, fans out 2-3 solution options with honest trade-offs, and — only after the user picks one and approves the draft — writes a delta-spec to `docs/` and MIGRATES it into runnable phase files as its finale, ending at the graph map with a ready dev command. It closes the loop "idea → spec → phases → (/mneme:dev)" without ever writing code or running dev itself. The internal fan mechanics (recall → options → trade-offs → recommendation) are borrowed from `/mneme:arch`. The difference: arch stops at the analysis and stays read-only; plan RECOMMENDS but the CHOICE is the user's, and plan continues — after that choice — all the way to a spec. plan does NOT replace arch; arch remains the think-only tool for architecture questions. Core requirement (this is the design's spine): the user wants to see solution options for EVERY task — even a small one — and to CONFIRM before any code. Whether a task is "obvious" is the USER's judgement, never the agent's. Hence two HARD gates inside this skill: a stop on the option choice, and a stop on the spec review. The skill PHYSICALLY does not continue past either without an explicit confirmation — the turn ends, and it is the user's move. ## Arguments `/mneme:plan "<task in words>"` — the task or change to plan, described in plain language. Examples: - `/mneme:plan "rename the m