pm-framework-selectorlisted

# PM framework selector This skill helps a PM (or someone helping a PM) pick the right framework for the decision in front of them. The repo's frameworks are organized by lifecycle phase, so framework selection starts by identifying what *kind* of decision is being made. ## How to apply 1. **Diagnose the question, not the symptom.** The user's surface question ("how do I prioritize these features?") may not be the real question ("we don't know what problem we're solving"). Ask one or two clarifying questions before recommending a framework. 2. **Map the decision to a lifecycle phase**, using the table below. Frameworks live in `frameworks/01-strategy-and-discovery.md` through `frameworks/05-continuous-prioritization.md`. 3. **Recommend 1–2 frameworks, not 5.** Cite the specific file in the repo. Explain *why* this framework, not just *what*. 4. **Note when not to use a framework.** One-way doors, strategic bets, and existential decisions usually need a memo, not a score. Flag this. | If the question is about... | The phase is... | Likely framework(s) | |---|---|---| | What problem to solve, why now, who for | Strategy & Discovery | PMF Narrative, Working Backwards, Pre-Mortem | | Whether the decision is reversible / how much rigor it deserves | Strategy & Discovery | One-Way / Two-Way Doors | | Risk surfacing before launch | Strategy & Discovery | Pre-Mortem (tigers / paper tigers / elephants), Sensitivity Analysis | | What to ship in V1 | Defining the MVP | JTBD Ranki