create-prompt-plan

# Create Prompt Plan Decompose a specification file into shell plans at `.turbo/plans/<spec-slug>-NN-<title>.md` plus an index at `.turbo/prompt-plans/<slug>.md`. Each shell represents one unit of work for a separate Claude Code session. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Resolve the source spec 2. Decompose into shells 3. Write shell files and the index 4. Run `/review-prompt-plan` skill 5. Run `/evaluate-findings` skill 6. Run `/apply-findings` skill 7. Present summary ## Step 1: Resolve the Source Spec Determine which spec to decompose using these rules in order: 1. **Explicit path** — If the user passed a file path, use it 2. **Explicit slug** — If a slug was passed, resolve to `.turbo/specs/<slug>.md` 3. **Single file** — Glob `.turbo/specs/*.md`. If exactly one file exists, use it 4. **Most recent** — If multiple files exist, use the most recently modified 5. **Legacy fallback** — If `.turbo/specs/` does not exist but `.turbo/spec.md` exists, use it 6. **Nothing found** — If no spec exists, tell the user to run `/create-spec` first and stop The slug of the resolved spec becomes the slug of the prompt plan: a spec at `.turbo/specs/<slug>.md` produces a prompt plan index at `.turbo/prompt-plans/<slug>.md` and shells at `.turbo/plans/<slug>-NN-<title>.md`. For the legacy fallback, use slug `legacy`. State the resolved spec path, target index path, and target shell directory before continuing. Read the spec and ident...