Skill.md
- SKILL.md
--- name: lean-ux-canvas description: Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next. ---
Library Skill.md library
Each one names the GitHub repo it came from, so you can check exactly what it tells your AI to do.
274990 Skill.md files
--- name: lean-ux-canvas description: Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next. ---
--- name: lifecycle-play-advisor description: Diagnose where a product sits in its lifecycle and which play fits — extend, replace, or retire. Use when a product is fading and you need the call, not just the worry. ---
--- name: market-landscape-scan description: Map a market's segments, players, substitutes, and whitespace with cited evidence. Use when entering or re-evaluating a market before sizing, positioning, or picking competitors to study. ---
--- name: opportunity-solution-tree description: Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build. ---
--- name: organic-growth-advisor description: Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next. ---
--- name: pestel-analysis description: Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy. ---
--- name: pestel-delta-monitor description: Quarterly re-scan of a prior PESTEL analysis. Use when checking which macro factors moved, which assumptions broke, and what's new — turning PESTEL from a workshop artifact into a radar. ---
--- name: pm-skill-creator description: Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill. ---
--- name: pol-probe-advisor description: Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort. ---
--- name: pol-probe description: Define a Proof of Life probe to test a risky hypothesis cheaply. Use when you need harsh truth before building real product. ---
--- name: porters-five-forces description: Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool. Use when weighing market entry or when margins erode and nobody can say why. ---
--- name: positioning-statement description: Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives. ---
--- name: positioning-workshop description: Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned. ---
--- name: prd-development description: Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative. ---
--- name: press-release description: Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet. ---
--- name: pricing-packaging-tracker description: Track competitor pricing and packaging as a diffable time series. Use when monitoring tiers, gates, limits, and price moves on a monthly or quarterly cadence. ---
--- name: prioritization-advisor description: Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach. ---
--- name: problem-framing-canvas description: Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions. ---
--- name: problem-statement description: Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD. ---
--- name: product-lifecycle-plays description: Map a product's lifecycle stage and choose between extension, replacement, and retirement plays. Use when a product is maturing or declining and the next move isn't obvious. ---
--- name: product-sense-interview-answer description: Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions. ---
--- name: product-strategy-session description: Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution. ---
--- name: proto-persona description: Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation. ---
--- name: recommendation-canvas description: Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning. Use when deciding whether an AI solution deserves investment or recommendation. ---