| name | collapse-unearned-complexity |
| description | Use when a structure has more moving parts than the job earns. Owns structural simplification only. |
| category | workflow |
| source_group | hermes-operational |
| compatibility | opencode |
When To Use
Load this when a structure has more moving parts than the job earns: extra layers, roles, processes, abstractions, prompts, documents, metrics, or governance that do not buy enough reliability.
The skill owns structural simplification. It removes unnecessary machinery while preserving the function that matters.
Do Not Use
Do not use this to force a decision, diagnose a broken system, calibrate tone, choose the user's mode, or package a recommendation. If the problem is not structural excess, do not collapse it.
What To Do
- Identify the job the structure must actually perform.
- Separate load-bearing parts from decorative or defensive parts.
- Remove, merge, or defer layers that do not change the outcome or reduce meaningful risk.
- Keep the smallest structure that still supports correct action, maintenance, and verification.
- Avoid replacing complexity with vagueness; the simplified form still needs a clear owner and check.
Output Shape
Return the simplification: current moving parts, what each buys, what can be removed, and the lean version that remains.
