product-strategy
Skill4 starsChanged 3 months agoMITView on GitHub
Prioritize features with positioning and RICE/MoSCoW. Use when prioritize features, what should we build first, roadmap, MoSCoW, or RICE.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- baekenough/oh-my-customcodetheir own version, first seen Nov 14, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- AntonioMellies/claude-code-skillstheir own version, first seen Nov 1, 2026
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- baov/proof-over-vibestheir own version, first seen Nov 1, 2026
Used with
Projects with it also use customer-journey-map, prd-writer and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nandanosqlSkillcustomer-journey-map
Map the complete customer experience across all touchpoints using the NNGroup framework. Identifies pain points, emotions, and opportunities at every stage of the user journey.
Also in 4 projects that use this
nimbalystSkillprd-writer
Create structured Product Requirements Documents (PRDs) with prioritized requirements. Use when writing product specs, feature requirements, or project briefs.
Also in 3 projects that use this
adolfoaranaes12Skillcreate-prd
Create comprehensive Product Requirements Documents (PRD) from high-level product ideas with structured market analysis, feature definition, and success metrics for both greenfield and brownfield contexts. Use when defining product vision for new projects (greenfield) or formalizing requirements for existing systems (brownfield).
Also in 3 projects that use this
LangChainSkillcompetitor-analysis
Analyze competitors in a given market segment. Trigger on: competitive landscape, competitor analysis, market comparison, competitive positioning.
Also in 3 projects that use this
birne-skSkillmarket-research
Professional market research and competitive analysis using McKinsey/BCG/Bain consulting methodologies. Use when analyzing markets, competitive landscapes, customer insights, or strategic positioning. Generates hypothesis-driven research with PPTX presentation deliverables.
Also in 3 projects that use this
SentrySkillmarketing-psychology
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- magnus919/agent-skills★ 177same name
- baekenough/oh-my-customcode★ 42same name
- aroyburman-codes/pm-skills★ 25same name
- yannickYamo/skills★ 23same name
- vignesh2027/Claude-Agentic-Skills2.0-version★ 6same name
- pedroromeroluna/ai-first-product-skills★ 5same name
- alunadev/ald-skills★ 4same name
- baov/proof-over-vibes★ 3same name
- ceeinbeta/pm-skills★ 3same name
- mcveloria/pm-skills★ 3same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- accessibility-reviewSkill
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- business-model-thinkingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-layout-patternsSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-system-builderSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- kinematic-motion-choreographySkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- security-privacy-reviewSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-hierarchy-reviewSkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Before finalizing the cut line:
- Distinctive: line 28
Tie-Breaking Rule: When two features have identical RICE scores, prioritize the one that eliminates friction on the existing critical path …
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Strategy
Strategy is saying no to good ideas so you can say yes to the right ones. A feature backlog without explicit prioritization is merely a wish list.
1. Articulate positioning (The Positioning Anchor)
Formulate the unequivocal product anchor:
"For [target persona], [Product Name] is a [product category] that [primary compelling value / superpower], unlike [status quo alternative] which [primary limitation of alternative]."
2. Harvest & normalize candidate features
Collect candidate items from product-discovery findings, stakeholder requests, and user feedback. Define each item as a discrete user capability, not a vague project theme.
3. Apply quantitative scoring (RICE Framework)
Score each feature using RICE methodology (See RICE-SCORING-GUIDE.md): $$\text{RICE Score} = \frac{\text{Reach} \times \text{Impact} \times \text{Confidence}}{\text{Effort}}$$
- Reach: Users impacted per quarter (e.g. 500 users).
- Impact: Massive (3x), High (2x), Medium (1x), Low (0.5x), Minimal (0.25x).
- Confidence: High (100%), Medium (80%), Low (50%).
- Effort: Person-months or sprint points estimate (e.g. 2).
4. Validate against Strategic OKRs & Tie-breaking
Before finalizing the cut line:
- Map each top-scoring item against current quarterly OKRs. High RICE items with zero OKR alignment are deferred.
- Tie-Breaking Rule: When two features have identical RICE scores, prioritize the one that eliminates friction on the existing critical path over the one introducing a brand-new surface area.
5. Establish the cut-line & explicit "Not Doing" list
Clearly segment features into:
- Now (Sprint / Phase 1): Above the cut-line.
- Next (Phase 2 Roadmap): High value, but waiting on upstream dependencies.
- Later / Won't Do: Documented explicit "No" with strategic rationale to prevent zombie feature creep.
Completion Criteria
- Positioning statement articulated with target user, category, and differentiator
- All features scored with Reach, Impact, Confidence, and Effort values
- High-ranking features validated against quarterly OKRs
- Tie-breaking rules applied to identical scores
- Explicit "Won't Do / Deferred" list generated with documented business rationale
Output Format
A product_strategy_one_pager.md artifact containing the positioning anchor, scored prioritization table, and explicit deferred list.
Anti-patterns
- Assigning 100% confidence to unvalidated assumptions.
- Treating effort as 1 for everything to manipulate the RICE score.
- Leaving low-priority items lingering in limbo without explicitly marking them as "Won't Do."
- Prioritizing executive pet features that score low on user reach and OKR alignment.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

