design-change
Design Change
Scope and Entry
Design one selected change, not the whole initiative. This standalone workflow must
be chosen, not silently substituted for the repository's lifecycle. Resolve process
conflicts first. A clear small change can enter directly without explore-idea or
slice-work; reuse settled requirements and do not restart an interview. For a
larger initiative, confirm direction and breakdown agreement before selecting scope.
Reuse the chosen document location. Otherwise use docs/work/<initiative>/ with
changes/001-slug/spec.md and changes/001-slug/plan.md. intent.md and roadmap.md
are optional when direct entry suffices. Create only this pair when useful; no empty
future scaffolding. Do not write production code in this phase. Experiments need
separate authorization; commits, pushes, and deployments are not authorized here.