Files
msd-core/docs/features/scope-reduction-detection.md
Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.
2026-10-06 01:47:40 +02:00

895 B

id, title, group
id title group
64 Scope Reduction Detection v1.31 Features

Part of: /msd-plan-phase

Purpose: Prevent silent requirement dropping during plan generation with three-layer defense.

Requirements:

  • REQ-SCOPE-01: System MUST prohibit planners from reducing scope without explicit justification
  • REQ-SCOPE-02: System MUST have plan-checker verify requirement dimension coverage
  • REQ-SCOPE-03: System MUST have orchestrator recover dropped requirements and re-inject them
  • REQ-SCOPE-04: System MUST implement three-layer defense: planner prohibition, checker dimension, orchestrator recovery

Process:

  1. Prohibit — Planner instructions explicitly forbid scope reduction
  2. Check — Plan-checker verifies all phase requirements are covered in the plan
  3. Recover — Orchestrator detects dropped requirements and re-injects them into the planning loop