Loading...
Loading...
Found 2 Skills
Use BEFORE coding any non-trivial change. Explores user intent, demand, tradeoffs, and approach. Produces a design doc in docs/design-docs/, not code. Required for LARGE tasks, optional for MEDIUM, skip for SMALL.
Audit goals, processes, systems, and plans for needless complexity — then recommend simplification only when it is warranted. Use when the user says "kiss", "keep it simple", "is this overcomplicated", "simplify this", or asks whether to cut scope/steps/architecture. Weigh risks and benefits of simplifying; do not default to reductionist cuts when complexity is earned. Simple also means a straightforward DAG to completion with right-sized tasks (not too small, not overly big). Pair with idk-now, recon, refactor-it, or agents design when the target is unclear or agent-shaped.