golem15/msd-core
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

enhance(#4089): add minimum-solution reasoning check (#4118)

Browse Source 
* enhance(planning): add minimum-solution reasoning check

* chore: add changeset for planning guidance

* chore: bind changeset to PR 4118

* docs: document planning sufficiency check

* docs: distinguish planning sufficiency guidance

---------

Co-authored-by: Tom Boucher <trekkie@nomorestars.com>
This commit is contained in:
Lorenz Leslie Espinosa
2026-09-08 20:58:23 -04:00
committed by GitHub
parent ff5c5782ee
commit b33df03726
4 changed files with 81 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
gsd-core/references/thinking-models-planning.md
View File

@@ -34,13 +34,29 @@ For each significant decision in this plan, ask what undoing it would cost three
This is the reasoning step that produces the rating. The taxonomy itself, the emission rules, and the anti-patterns live in @~/.claude/gsd-core/references/planner-reversibility.md — do not maintain a second classification here.
## 5. Curse of Knowledge Counter
## 5. Occam's Razor
**Counters:** Plans that prescribe avoidable dependencies, abstractions, files, or speculative flexibility before execution begins.
This check complements the planner's RESEARCH.md `dont_hand_roll` guidance and the plan checker's Dimension 12 (Pattern Compliance): those sources identify capabilities and established patterns, while this check orders otherwise sufficient implementation choices. The executor applies the related check later in `thinking-models-execution.md`, after the plan has already selected an approach.
After preserving locked user decisions and complete requirement coverage, choose the first option that is demonstrably sufficient for the task's `<done>` condition:
1. Existing project behavior, helper, or established pattern
2. Standard-library capability
3. Native platform capability
4. Already-installed dependency
5. Minimum new implementation
This ordering is a sufficiency check, not permission to make the task smaller. It must never reduce requested scope or override locked user decisions, requirement coverage, security, validation, accessibility, error handling, or verification. The planner uses it when choosing implementation actions; the plan checker flags a new abstraction or dependency only when a higher rung is demonstrably sufficient.
## 6. Curse of Knowledge Counter
**Counters:** Plan-to-executor ambiguity from compressed instructions.
For each `<action>` step, re-read it as if you have NEVER seen this codebase. Is every noun unambiguous (which file? which function? which endpoint?)? Is every verb specific (add WHERE? modify HOW?)? If a step could be interpreted two ways, rewrite it. Include file paths, function names, and expected behavior in every action step.
## 6. Base Rate Neglect Counter
## 7. Base Rate Neglect Counter
**Counters:** Planners ignoring low-confidence research caveats.