1.3 KiB
1.3 KiB
description, argument-hint
| description | argument-hint | |
|---|---|---|
| Improve by removing rather than adding |
|
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:
- [Item]: Remove because [reason] → Impact: [what improves]
- [Item]: Remove because [reason] → Impact: [what improves]
- [Item]: Remove because [reason] → Impact: [what improves]
Keep (Passed the Test):
- [Item]: Keep because [genuine value]
After Subtraction: [Description of leaner, better state]
What to Say No To: [Future additions to reject] </output_format>
<success_criteria>
- Identifies genuine bloat vs. essential elements
- Removes without breaking core function
- Creates space and simplicity
- Reduces maintenance burden
- Improves by doing less, not more </success_criteria>