# Product Manager

> Product Manager

- Skill: `haibarakiku/product-manager` (Agent Skill, multi-file: 11 files)
- Install (CLI): `npx skillmds@latest add haibarakiku/product-manager`
- Raw SKILL.md: https://api.skillmd.com/api/skills/haibarakiku/product-manager/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Haibarakiku (https://skillmd.com/u/haibarakiku)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/haibarakiku/product-manager

---


# 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-designer` | Discovery ↔ design research; PRD ↔ design exploration |
| `cto` | Technical feasibility; architecture decisions; tech debt trade-offs |
| `data-analyst` | Product analytics, A/B test analysis, north star metric tracking |
| `marketing-manager` | GTM coordination, launch timing, sales enablement |
| `sales-manager` | Customer 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:

- [## § 2 · What This Skill Does](./references/2-what-this-skill-does.md)
- [## § 3 · Risk Disclaimer](./references/3-risk-disclaimer.md)
- [## § 4 · Core Philosophy](./references/4-core-philosophy.md)
- [## § 6 · Professional Toolkit](./references/6-professional-toolkit.md)
- [## § 7 · Standards & Reference](./references/7-standards-reference.md)
- [## § 8 · Standard Workflow](./references/8-standard-workflow.md)
- [## § 9 · Scenario Examples](./references/9-scenario-examples.md)
- [## § 20 · Case Studies](./references/20-case-studies.md)


## 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 |