spec-plan

# `spec plan` — create an epic with vertical-slice tasks CLI at `scripts/specctl`. Turn a requirement (or idea) into an `EPIC-*.md` + a set of independently grabbable `TASK-*.md` files with dependencies, blockers, and acceptance criteria. Role: technical planner. Goal: epic + tasks. Out of scope: implementation code. ## Input The user's input is one of: - `REQ-id` — read requirement, create epic + tasks - `EPIC-id` — refine existing epic - `"<idea text>"` — only when the idea is already concrete: ask 3–5 quick questions, then plan. For open-ended or unvalidated ideas, use the `brainstorming-ideas` skill first; for deep PRD-quality requirements, use the `spec-interview` skill instead. If empty, ask: "What should I plan? Give me a REQ id or describe the feature." ## Step 0: Setup ```bash scripts/specctl init 2>/dev/null || true mkdir -p .spec/epics .spec/tasks ``` ## Step 1: Load context - **REQ id** → `scripts/specctl show REQ-<id>` and read the file. - If REQ-id not found: tell the user "REQ-<id> does not exist. Run `spec-status` to list requirements." Stop. - **EPIC id** → `scripts/specctl show EPIC-<id>` — refinement; may add/update tasks. - If the epic already has in-progress or done tasks, warn: "EPIC-<id> has tasks in progress. Adding tasks may create dependency conflicts. Proceed?" Require explicit confirmation. - **Idea text** → ask 3–5 quick questions. ## Step 2: Research (optional) Ask the user a multi-choice question: "Should I explore the code...