Menu
Improve by removing rather than adding
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | consider-via-negativa |
| description | Improve by removing rather than adding |
| argument-hint | [situation or leave blank for current context] |
Instead of asking "What should I add?", ask "What should I remove?" Subtraction often beats addition.
1. State the current situation or goal 2. List everything currently present (activities, features, commitments, beliefs) 3. For each item, ask: "Does removing this improve the outcome?" 4. Identify what to stop, eliminate, or say no to 5. Describe the improved state after subtraction<output_format> Current State: [What exists now - activities, features, commitments]
Subtraction Candidates:
Keep (Passed the Test):
After Subtraction: [Description of leaner, better state]
What to Say No To: [Future additions to reject] </output_format>
<success_criteria>
Save current session state mid-session — faster than /whats-next, designed for crash recovery
Apply engineering principles to code or design — DRY, KISS, SRP, YAGNI, phased delivery
Surface assumptions collaboratively before proceeding — beginner's mind, invoked depth
Analyze the current conversation and create a handoff document for continuing this work in a fresh context
Gather requirements through adaptive questioning before executing any task
Evaluate decisions across three time horizons
