ccc-planlisted

# /ccc-plan — Feature Planning Flow User has an idea. Job: turn it into a structured plan file before any code gets written. We cascade through a spec interview, then fire the `planner` agent in the background to produce the plan at the **session-bound path** returned by `EnterPlanMode` — so it renders in Claude Code Desktop's native Plan pane. Return a one-line summary + path. This is the "evals before specs before code" gate. Every multi-day feature routes through here. ## Step 0 — Detect and enter plan mode (ALWAYS first) Before showing any UI, determine the session plan file path: **If "Plan File Info" block is present in the system-reminder context** (Desktop already activated plan mode for this session, surfacing a path like `~/.claude/plans/<whimsy-name>.md`): - Capture that path as `PLAN_PATH` - Do NOT call `EnterPlanMode` again — it is already active **If NO "Plan File Info" block is detected:** - Call the `EnterPlanMode` tool — this switches the session into plan mode - `EnterPlanMode` returns the session-bound path (e.g., `~/.claude/plans/spirited-oak-forest.md`) - Capture that returned path as `PLAN_PATH` `PLAN_PATH` is the canonical write target for the rest of this skill. Do not write to any other path under `~/.claude/plans/`. > **Why this matters:** Desktop's native Plan pane only reads the session-bound path it created. Writing to a fixed `~/.claude/plans/ccc-<date>-<slug>.md` path produces a plan the pane cannot find — it shows "no plan yet" even aft