op-preparelisted

# op-prepare — the planning pass One dedicated planning session before any code. Output is plan files in `docs/`, nothing else. Done right, every subsequent session is cold-start-resistant and scope-locked. Full step-by-step pass: [`procedure.md`](procedure.md). ## When to fire - `/prep` (with or without a section name) → run the procedure. - User says "I want to build X", "let's start a new project", "let's plan the next big feature", "scope this out", "I have an idea for…" → confirm "planning pass — no code?" then run the procedure. - Existing project has `docs/PROJECT_BRIEF.md` but no `docs/PROJECT_PLAN.md`, or a major new section has no plan file → run scoped to what's missing (`/prep <section-name>` variant). ## When NOT to fire - User just wants to code now — push back once on the upfront cost; if still no, hand off to `op-workflow`. - Plans already exist and section work is mid-flight — the ambient `op-spine-active` skill carries the session. - Brownfield codebase the user hasn't explored — fire `op-brownfield` first; plan rewrites/extensions only after discovery. - **Work shape is not Build** (audit, refactor, migration, investigation, research, cleanup) — `op-approach` fires *before* this skill on those shapes, identifies the shape, and routes back here informed by the shape's phase structure + hard rule. See [`chapters/workflow/05k-work-shapes.md`](../../../chapters/workflow/05k-work-shapes.md). ## What to read first In this order, before drafting anything: