make_plan

# Implementation Plan Creation (`make_plan`) Create a detailed, multi-document implementation plan for a software feature or task. This skill covers plan **creation** only. To **execute** a finished plan, use the **exec_plan skill**. > **CodeOps Skills Version**: 3.19.0 ## What you produce A folder `plans/<feature-name>/` containing: ``` plans/<feature-name>/ ├── 00-ambiguity-register.md # Zero-Ambiguity Gate register (audit trail) ├── 00-index.md # Overview and navigation ├── 01-requirements.md # Requirements and scope ├── 02-current-state.md # Current implementation analysis ├── 03-XX-<component>.md # Technical spec per component (one or more) ├── 07-testing-strategy.md # Spec test cases + verification └── 99-execution-plan.md # Phases, sessions, task checklist ``` The full templates for every document live in **[templates.md](templates.md)** — read it before writing any plan document in Phase 2. ## Resolve paths first (layout-aware) Determine the layout via **[../../_shared/layout-convention.md](../../_shared/layout-convention.md)** before creating the plan folder: - **Flat layout** (no marker): the plan folder is `plans/<feature-name>/`; `00-index.md` declares `> **Implements**: RD-NN` — exactly as flat layout always has. - **Nested layout** (marker present): the plan folder is `codeops/features/<f>/plans/<plan>/`. **Ask/confirm the target feature** first (create the feature folder lazily if new — never guess). `00-...