# Plan Map **Iteration:** 9, Scoping **Intent:** Scope an engagement from a scope spec: a structured file that may arrive complete, partly filled or not at all, completed in conversation and approved by the customer before requirements begin. So that a design's quality no longer rests on what the agents had to assume. **Status:** step 1 built on 2026-10-11, not run with real models; steps 2 to 6 planned **This directory covers:** steps 1 to 6 ## Sources of truth - `docs/adr/0008-scoping-starts-from-a-scope-spec.md`: the decisions. - `.scratch/scoping-and-work-breakdown/spec.md`: the design, including the draft spec, the owner's own example and how the two were combined. - `skills/scoping/assets/catalogue.yaml`: every field a scope spec may hold. ## Status | Step | What | Status | |---|---|---| | 1 | The catalogue, reading and validating a spec, the gap list, the two files beside the Intent, run options from the spec, the spec shown to every Specialist | built 2026-10-11 (`steps/step-1.md`); not run with real models | | 2 | The conversation that fills gaps and writes answers into the completed copy; scoping as a Phase with its Deliverable and Approval; a spec drafted from a sentence | planned | | 3 | Requirements traced to the customer's requirement ids and to spec fields, in `requirements.json`; readiness in the solution guide | planned | | 4 | An edited spec as a Change request, compared field by field | planned | | 5 | Evaluation cases as specs, replacing answers matched by pattern | planned; `case-08-landing-zone` is the first | | 6 | The status `BASELINE_LOCKED` set when the Execution completes | planned | ## Dependency graph - Step 1: no dependencies - Step 2: depends on step 1 - Step 3: depends on step 1 - Step 4: depends on step 1, iteration 7 - Step 5: depends on step 1 - Step 6: depends on step 2 The work breakdown structure is iteration 10 and uses the spec's `delivery` section from step 1.