Marketplace

product

Product workflows router. Use when user mentions "PRD", "competitive analysis", "metrics", "OKRs", "cohort", "requirements", or "technical debt". Triggers on product management and strategy tasks.

$ 安裝

git clone https://github.com/saadshahd/moo.md /tmp/moo.md && cp -r /tmp/moo.md/product/skills/product ~/.claude/skills/moo-md

// tip: Run this command in your terminal to install the skill

SKILL.md

View on GitHub →

name: product description: Product workflows router. Use when user mentions "PRD", "competitive analysis", "metrics", "OKRs", "cohort", "requirements", or "technical debt". Triggers on product management and strategy tasks.

Product Skill

Router skill for product management workflows. Detects task type and routes to appropriate workflow.

When This Skill Activates

You're working on:

Competitive analysis or market positioning
Product requirements documentation
Goal setting and metrics definition
User research synthesis
Cohort and retention analysis
PRD quality evaluation
Technical debt prioritization

Workflow Selection

Announce which workflow you're using:

Task Type	Workflow	Reference
Competitive analysis, market gaps, win/loss	Competitive Analysis	`references/compete.md`
Feature specs, requirements, MVP scoping	PRD Generation	`references/prd.md`
Goals, OKRs, KPIs, tracking systems	Metrics & Goals	`references/metrics.md`
User interviews, qualitative data, insights	Research Synthesis	`references/research.md`
Retention, LTV, churn, cohort data	Cohort Analysis	`references/cohort.md`
PRD review, completeness check, scoring	PRD Evaluation	`references/prd-eval.md`
Tech debt triage, remediation planning	Debt Prioritization	`references/debt.md`

Related Thinking Tools

From hope/skills/soul/references/tools/:

Tool	When to Use
Second-Order Thinking	Predict consequences of product decisions
Pre-Mortem	Anticipate launch failures
Impact-Effort	Focus on high-impact, low-effort features

From this skill's references/:

Tool	When to Use
Jobs To Be Done	Understand what customers hire products for
Systems Archetypes	Recognize "limits to growth", "shifting burden" patterns

Usage

Detect which workflow applies based on user's task
Announce: "I'm using the product skill for [workflow]"
Load the appropriate reference file
Execute the workflow exactly as written

Rules

Use Ask tool to gather input before proceeding
Ground recommendations in evidence
Use story points, never time estimates
Challenge assumptions and cut scope by default