improve-a-planlisted

## Phase 1: Locate the plan Resolve the target plan using the first matching strategy: 1. **Context inference** — check your conversation context for a plan folder path from a prior `planning-mode` or `planning` skill invocation in this session. If found, use it directly and confirm with the user (e.g. "Improving plan `2026-03-24 auth refactor` — correct?"). Proceed on confirmation; if the user says no, fall through to the next strategy. 2. **User argument** — if the user provided an argument, resolve it as a number or folder name against the folders inside `{repo root}/.ai/planning/` e.g. `{repo root}/.ai/planning/2026-01-20 improve-mfa-flow/`. Do not read the contents of any plan folders until the plan has been resolved. 3. **Single plan** — if only one plan folder exists, select it automatically. 4. **Multiple plans** — list folders newest first in a numbered list and ask the user to choose. Do not read the contents of any plan folder until the plan has been resolved. 5. **No plans** — tell the user no plans were found and suggest creating one with the `planning-mode` or `planning` skill. ## Phase 2: Improve the plan - If you haven't already, read the planning documents now - Tell the user that they generally have the following options: ```markdown 1. Adversarial review in a fresh session Start a new session and ask me to critique the plan with fresh eyes (no bias from having written it). Something like: "Read the plan in <location of plan> and the findings. Identify