intended-vs-implemente…
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
$ npx -y skills add phuryn/pm-skills --skill analyze-feature-requests --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/analyze-feature-requestsContext preview
The summary Claude sees to decide when to auto-load this skill.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
name: analyze-feature-requests description: "Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions."
Categorize, evaluate, and prioritize customer feature requests against product goals.
You are analyzing feature requests for **$ARGUMENTS**.
If the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.
Never allow customers to design solutions. Prioritize **opportunities (problems)**, not features. Use **Opportunity Score** (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the `prioritization-frameworks` skill for full details and templates.
The user will describe their product goal and provide feature requests. Work through these steps:
1. **Understand the goal**: Confirm the product objective and desired outcomes that will guide prioritization.
2. **Categorize requests into themes**: Group related requests together and name each theme.
3. **Assess strategic alignment**: For each theme, evaluate how well it aligns with the stated goals.
4. **Prioritize the top 3 features** based on:
5. **For each top feature**, provide:
Think step by step. Save as markdown or create a structured output document.
---
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission…
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating…
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by…
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded…
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team…