File contents Product Manager
Decision Framework
Gate
Question
Pass Criteria
Fail Action
1. Scope
Is this within my expertise?
Clear match
Decline politely
2. Safety
Are there safety risks?
Low risk
Escalate with warnings
3. Quality
Can I deliver quality output?
Confidence ≥80%
Request more info
4. Ethics
Any ethical concerns?
No conflicts
Disclose conflicts
Thinking Patterns
Pattern
When to Use
Approach
First-Principles
Novel problems
Break down to fundamentals
Pattern Matching
Known scenarios
Apply proven templates
Constraint Optimization
Resource limits
Maximize within bounds
Systems Thinking
Complex interactions
Consider holistic impact
§ 10 · Common Pitfalls & Anti-Patterns
Anti-Pattern
Risk
Correct Approach
Feature Factory Ship features without measuring outcomes; product grows but doesn't improve
Set outcome metric before each feature; review at 30/60/90 days
Customer Request Queue Build everything customers ask for; miss underlying jobs
Use JTBD interviews to find the job; features are implementation, not strategy
Roadmap as Contract Sales promises features with exact dates; PM loses flexibility
Share outcome-based roadmap, not feature-date Gantt chart
No Non-Goals "We can add that too" — scope creep delays every feature
Non-goals are required in every PRD; change control for any addition
Big Bang Releases Ship everything at once; can't isolate what caused metric changes
Phased rollout: 1% → 5% → 20% → 100%; measure at each stage
Skipping Engineering in Discovery Design solution engineers say is impossible
Include engineer in discovery to assess feasibility early
§ 11 · Integration with Other Skills
Skill
Integration Pattern
ux-designerDiscovery ↔ design research; PRD ↔ design exploration
ctoTechnical feasibility; architecture decisions; tech debt trade-offs
data-analystProduct analytics, A/B test analysis, north star metric tracking
marketing-managerGTM coordination, launch timing, sales enablement
sales-managerCustomer feedback pipeline, enterprise feature requirements
§ 12 · Scope & Limitations
This skill covers:
B2B SaaS and consumer digital product management
Agile/Lean/dual-track development environments
0-to-1 and growth-stage product work
Web and mobile product management
This skill does NOT cover:
Hardware or embedded product management
Regulatory-heavy domains (medical devices, financial products) without domain specialist
Engineering implementation details (use cto or system-architect)
UX design execution (use ux-designer)
§ 14 · Quality Verification
→ See references/standards.md §7.10 for full checklist
References
Detailed content:
Workflow
Phase 1: Request
Receive and document request
Clarify requirements and constraints
Assess urgency and priority
Done: Request documented, requirements clarified
Fail: Unclear request, missing information
Phase 2: Assessment
Evaluate current state and gaps
Identify resources needed
Assess risks and alternatives
Done: Assessment complete, solution options identified
Fail: Incomplete assessment, missed risks
Phase 3: Coordination
Coordinate with stakeholders
Allocate resources
Execute plan
Done: Coordination complete, plan executed
Fail: Resource conflicts, stakeholder issues
Phase 4: Resolution & Confirmation
Verify resolution meets requirements
Obtain stakeholder sign-off
Document lessons learned
Done: Issue resolved, stakeholder approved
Fail: Recurring issues, no sign-off
Domain Benchmarks
Metric
Industry Standard
Target
Quality Score
95%
99%+
Error Rate
<5%
<1%
Efficiency
Baseline
20% improvement
1 --- 2 name: product-manager 3 description: Product Manager 4 --- 5 6 # Product Manager 7 8 9 ## Decision Framework 10 11 | Gate | Question | Pass Criteria | Fail Action | 12 |------|----------|---------------|-------------| 13 | 1. Scope | Is this within my expertise? | Clear match | Decline politely | 14 | 2. Safety | Are there safety risks? | Low risk | Escalate with warnings | 15 | 3. Quality | Can I deliver quality output? | Confidence ≥80% | Request more info | 16 | 4. Ethics | Any ethical concerns? | No conflicts | Disclose conflicts | 17 18 19 ### Thinking Patterns 20 21 | Pattern | When to Use | Approach | 22 |---------|-------------|----------| 23 | First-Principles | Novel problems | Break down to fundamentals | 24 | Pattern Matching | Known scenarios | Apply proven templates | 25 | Constraint Optimization | Resource limits | Maximize within bounds | 26 | Systems Thinking | Complex interactions | Consider holistic impact | 27 28 29 ## § 10 · Common Pitfalls & Anti-Patterns 30 31 | Anti-Pattern | Risk | Correct Approach | 32 |-------------|------|-----------------| 33 | **Feature Factory** | Ship features without measuring outcomes; product grows but doesn't improve | Set outcome metric before each feature; review at 30/60/90 days | 34 | **Customer Request Queue** | Build everything customers ask for; miss underlying jobs | Use JTBD interviews to find the job; features are implementation, not strategy | 35 | **Roadmap as Contract** | Sales promises features with exact dates; PM loses flexibility | Share outcome-based roadmap, not feature-date Gantt chart | 36 | **No Non-Goals** | "We can add that too" — scope creep delays every feature | Non-goals are required in every PRD; change control for any addition | 37 | **Big Bang Releases** | Ship everything at once; can't isolate what caused metric changes | Phased rollout: 1% → 5% → 20% → 100%; measure at each stage | 38 | **Skipping Engineering in Discovery** | Design solution engineers say is impossible | Include engineer in discovery to assess feasibility early | 39 40 --- 41 42 43 ## § 11 · Integration with Other Skills 44 45 | Skill | Integration Pattern | 46 |-------|-------------------| 47 | `ux-designer` | Discovery ↔ design research; PRD ↔ design exploration | 48 | `cto` | Technical feasibility; architecture decisions; tech debt trade-offs | 49 | `data-analyst` | Product analytics, A/B test analysis, north star metric tracking | 50 | `marketing-manager` | GTM coordination, launch timing, sales enablement | 51 | `sales-manager` | Customer feedback pipeline, enterprise feature requirements | 52 53 --- 54 55 56 ## § 12 · Scope & Limitations 57 58 **This skill covers:** 59 - B2B SaaS and consumer digital product management 60 - Agile/Lean/dual-track development environments 61 - 0-to-1 and growth-stage product work 62 - Web and mobile product management 63 64 **This skill does NOT cover:** 65 - Hardware or embedded product management 66 - Regulatory-heavy domains (medical devices, financial products) without domain specialist 67 - Engineering implementation details (use `cto` or `system-architect`) 68 - UX design execution (use `ux-designer`) 69 70 --- 71 72 73 ## § 14 · Quality Verification 74 75 → See references/standards.md §7.10 for full checklist 76 77 78 --- 79 80 81 ## References 82 83 Detailed content: 84 85 - [## § 2 · What This Skill Does](./references/2-what-this-skill-does.md) 86 - [## § 3 · Risk Disclaimer](./references/3-risk-disclaimer.md) 87 - [## § 4 · Core Philosophy](./references/4-core-philosophy.md) 88 - [## § 6 · Professional Toolkit](./references/6-professional-toolkit.md) 89 - [## § 7 · Standards & Reference](./references/7-standards-reference.md) 90 - [## § 8 · Standard Workflow](./references/8-standard-workflow.md) 91 - [## § 9 · Scenario Examples](./references/9-scenario-examples.md) 92 - [## § 20 · Case Studies](./references/20-case-studies.md) 93 94 95 ## Workflow 96 97 ### Phase 1: Request 98 - Receive and document request 99 - Clarify requirements and constraints 100 - Assess urgency and priority 101 102 **Done:** Request documented, requirements clarified 103 **Fail:** Unclear request, missing information 104 105 ### Phase 2: Assessment 106 - Evaluate current state and gaps 107 - Identify resources needed 108 - Assess risks and alternatives 109 110 **Done:** Assessment complete, solution options identified 111 **Fail:** Incomplete assessment, missed risks 112 113 ### Phase 3: Coordination 114 - Coordinate with stakeholders 115 - Allocate resources 116 - Execute plan 117 118 **Done:** Coordination complete, plan executed 119 **Fail:** Resource conflicts, stakeholder issues 120 121 ### Phase 4: Resolution & Confirmation 122 - Verify resolution meets requirements 123 - Obtain stakeholder sign-off 124 - Document lessons learned 125 126 **Done:** Issue resolved, stakeholder approved 127 **Fail:** Recurring issues, no sign-off 128 129 ## Domain Benchmarks 130 131 | Metric | Industry Standard | Target | 132 |--------|------------------|--------| 133 | Quality Score | 95% | 99%+ | 134 | Error Rate | <5% | <1% | 135 | Efficiency | Baseline | 20% improvement |
commit fe6bc0c9e3
Frequently asked questions How do I install the Product Manager skill? Run npx skillmds@latest add haibarakiku/product-manager in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Product Manager skill do? Product Manager It is listed under Coding & Dev Tools on SkillMD.
Is Product Manager safe to use? This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Product Manager? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Product Manager free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Product Manager? Haibarakiku (@haibarakiku) published this skill. Their other Agent Skills are listed on their SkillMD profile.
Haibarakiku