gpt56-stop-overengineeringlisted
Install: claude install-skill Swallow100/gpt-5.6-stop-overengineering
# GPT-5.6 Stop Overengineering
Make the smallest safe change. Produce proportionate proof. Then stop.
## 1. Lock the contract
Before editing, reduce the task to four lines:
- **Outcome:** the observable result the user requested.
- **Scope:** the files, behavior, or subsystem that owns that result.
- **Constraints:** explicit limits plus repository instructions.
- **Proof:** the least expensive evidence that can establish success.
Infer these from available context when they are clear. Ask only when a missing answer would materially change the implementation or create meaningful risk.
Do not silently add goals. Treat appealing improvements as optional follow-ups, not requirements.
## 2. Choose the smallest sufficient change
Prefer, in order:
1. Reuse an existing path, pattern, or dependency.
2. Modify the narrowest ownership boundary.
3. Add the least new code needed for the requested behavior.
Do not add an abstraction for one hypothetical future use. Do not introduce a dependency, framework, configuration surface, public API, migration, compatibility layer, or broad refactor unless the contract requires it.
Preserve unrelated code, formatting, comments, and user changes. Avoid cleanup whose only justification is "while here."
Before expanding into another subsystem or materially growing the expected diff, pause and either choose a narrower solution or request approval.
## 3. Verify in proportion to risk
Select the lowest tier that can realistically catch a reg