majiayu000 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
- Game-changing feature ideation
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 |
| Breakthrough features, innovation ideation | Game-Changing Features | references/game-changing-features.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 with confirmation gates (see below)
Confirmation Gates
Multi-step workflows pause at checkpoints to prevent wasted work when intent drifts.
Gate Points:
| Phase | Gate |
|---|---|
| After research/discovery | ⚠️ CHECKPOINT: "Does this understanding match your intent?" |
| After approach selection | ⚠️ CHECKPOINT: "Here's my proposed approach. Should I proceed?" |
| Before final artifact | ⚠️ CHECKPOINT: "Ready to generate final output. Confirm?" |
Skip gates: Say "proceed without confirmation" to run uninterrupted.
In workflows: Each reference file should pause at these points:
### Phase 2: Analysis
[... phase content ...]
⚠️ **CHECKPOINT**: Present findings summary. Ask: "Does this capture the key insights? Any adjustments before I continue?"
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