the-courage-to-delete

name

the-courage-to-delete

description

This skill should be used when the user wants help subtracting — identifying what to cut, delete, or deprioritize so the core product can breathe again. Responds to "what should I cut", "this is too bloated", "what can I delete", "simplify this", "what's diluting the core", "what would this look like with less", or any moment when a product, feature set, or roadmap is crowded, overcommitted, or accumulating obligations faster than conviction.

The Courage to Delete

Overview

This skill helps the user subtract well.

Most systems are built to add: more features, more flows, more promises, more structure. This skill asks the harder question: what is making the thing weaker by merely existing?

When to Use

Use this when:

• the product feels bloated
• the core value is getting harder to see
• a roadmap is accumulating obligations faster than conviction
• the team needs help saying no to already-present things

Do not use this as an excuse for aesthetic minimalism. Deleting is only good when it strengthens the essence of the product.

What to Produce

Identify:

• the core promise
• what currently supports it
• what currently dilutes it
• candidate deletions
• what gets stronger if those pieces go away

When useful, show two shapes:

• the current wider version
• the leaner, more legible version

Working Loop

1. State the core promise. What is the product most deeply trying to do for the user?

2. Sort the current parts. Which pieces intensify that promise, and which merely coexist with it?

3. Identify dilution. Look for features that split attention, create extra obligations, or make the product keep too many promises at once.

4. Show the stronger smaller shape. Do not just say "delete this." Explain what becomes clearer, lighter, or more legible if it goes away.

Suggested Output Shape

• Core promise
• What strengthens it
• What dilutes it
• Delete / keep / maybe later
• What the leaner version gains

Tiny Example

• Core promise: Help small teams publish clean release notes fast.
• What strengthens it: Fast drafting, approval, and export.
• What dilutes it: Built-in roadmap planning and chat.
• Delete / keep / maybe later: Delete chat, keep export, maybe later add lightweight comment threads.
• What the leaner version gains: The product becomes easier to explain and easier to trust.

Working Style

• Be honest without being macho about subtraction
• Explain why removal helps
• Distinguish "not core" from "bad"
• Protect the project from keeping too many promises at once
• Voice: follow VOICE.md in this directory — gentle truth-telling, warm precision, calm confidence, natural language

Common Mistakes

• Confusing subtraction with taste-signaling minimalism
• Recommending deletion without naming the core promise first
• Treating everything non-core as worthless
• Failing to show what the stronger reduced version actually looks like

Good Outcome

The user should feel:

• "I can finally see what this should stop trying to be"
• "removing that would actually make the whole thing breathe"
• "this helped me choose the harder, cleaner path"