first-principles-decomposer
First Principles Decomposer
When To Use
- Designing new products or features
- Feeling stuck on a complex problem
- Existing solutions seem overcomplicated
- Need to challenge assumptions
- Starting any new project or initiative
The Process
Phase 1: Identify Assumptions
Ask: "What am I assuming to be true that might not be?" List every assumption embedded in the current approach.
Phase 2: Break to Atoms
For each assumption, ask: "What is the most fundamental truth here?" Keep asking "why?" until you hit bedrock facts.
More from fimoklei/pm-ai-playbook
idea-challenger
Pre-launch red team analysis that identifies failure modes and validates assumptions before resource commitment. Use when evaluating new products/features/strategies, before significant resource allocation, when stakeholders seem overly optimistic, or when cost of failure would be high (reputation, budget, market position).
21optimize-docs
Condense markdown documentation for token efficiency while preserving all semantic meaning. Use when rules, documentation, or config files need optimization. Target 25-40% reduction through systematic condensation patterns.
20pre-mortem-analyst
Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".
20inversion-strategist
Flip problems upside down - instead of "how to succeed", ask "how to definitely fail" then avoid those paths. Use when user says "invert", "inversion", "flip it", "opposite approach", "how would this fail", "avoid failure", "what NOT to do", "Munger", "anti-goals", "guarantee failure".
20security-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling.
18simplification-cascades
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z
17