Some checks failed
validation / verify (push) Failing after 10s
Every Execution now begins by agreeing the scope, before requirements. - A new Phase and Deliverable, produced by a scope analyst with two tools: scope_read shows what is settled and what is not; scope_set records fields with where each value came from (the request, the customer's answer, or an assumption with its reason). Code checks each value against the catalogue. - With someone present the analyst asks for what is missing; with nobody present it assumes it, visibly. With no spec it drafts one from the request. A value the customer stated in the file is changed only by their own answer. - A submission cannot leave an essential field unknown. Code writes the completed spec, the data every later Specialist reads, and the information register, from what was recorded. - The spec's status follows the Execution: under review, approved, then locked as a Baseline. A Change request starts from the delivered scope. - The requirements analyst derives from the agreed scope and no longer asks for what it settles. About 80 tests assumed requirements came first; tests/scoped.py runs scoping ahead of a test's own script, and tests about order and counts are updated. Not run with real models. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
35 lines
2.0 KiB
Markdown
35 lines
2.0 KiB
Markdown
# 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:** steps 1, 2 and 6 built on 2026-10-11, not run with real models; steps 3 to 5 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 | built 2026-10-11 (`steps/step-2.md`); not run with real models |
|
|
| 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 | built with step 2 |
|
|
|
|
## 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.
|