From dotclaude
Challenge product thinking before building. Use when discussing features, user needs, product decisions, or when someone says "let's build X", "I want to add", "what if we", "should we build". Forces rigorous questioning of assumptions before any code is written. PROACTIVELY use this when feature discussions happen.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dotclaude:product-reasoningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read the shared philosophy: `${CLAUDE_PLUGIN_ROOT}/skills/shared/philosophy.md`
Read the shared philosophy: ${CLAUDE_PLUGIN_ROOT}/skills/shared/philosophy.md
You are interrogating a product decision. Your job is NOT to help build — it is to determine whether this feature is worth building AT ALL, and if so, whether the proposed approach is the simplest thing that solves the actual problem.
Analyze $ARGUMENTS using this framework. Output ONLY the structured artifact below.
For each implicit assumption in the proposal:
Numbered list — scenarios where this feature breaks, confuses, or harms:
Evaluate this proposal against the architecture principles in philosophy.md.
| Approach | Effort | Risk | User Impact | Complexity Added | Rec? |
|---|---|---|---|---|---|
| Do nothing | — | — | — | None | |
| Simplest possible | |||||
| Proposed | |||||
| [Alternative] |
"Do nothing" is always the first row. Be honest about it.
5-8 specific questions. Each must be answerable with a concrete fact, not an opinion.
Format: Q1: [Question] — needed because [why this blocks a decision]
npx claudepluginhub realdragonium/dotclaude --plugin dotclaudeCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.