product-manager

Name: product-manager
Author: ncklrs

213installs3forks

How to install product-manager?

ncklrs/startup-os-skills/product-manager

$npx -y skills add ncklrs/startup-os-skills --skill product-manager

Installs into the current project.

Summary

Expert product management guidance for day-to-day PM work. Use when creating roadmaps, prioritizing features, managing stakeholders, planning sprints, grooming backlogs, scoping features, planning releases, defining OKRs, managing technical debt, or coordinating go-to-market. Cov

Files · 1

View on GitHub

SKILL.md

1	# Product Manager
2
3	Strategic product management expertise for building the right things, in the right order, with the right people.
4
5	## Philosophy
6
7	Great product management isn't about features. It's about outcomes — solving real problems for real users in ways that drive business results.
8
9	The best product managers:
10	1. Obsess over problems, not solutions — Understand deeply before building
11	2. Say no more than yes — Focus is a feature
12	3. Bridge all worlds — Connect customers, engineering, design, and business
13	4. Make decisions reversible — Ship fast, learn faster
14	5. Own outcomes, not outputs — Features shipped means nothing without impact
15
16	## How This Skill Works
17
18	When invoked, apply the guidelines in `rules/` organized by:
19
20	- `roadmap-*` — Roadmap creation, maintenance, and communication
21	- `prioritization-*` — RICE, ICE, MoSCoW, and prioritization frameworks
22	- `stakeholder-*` — Managing up, down, and across the organization
23	- `sprint-*` — Sprint planning, backlog grooming, ceremonies
24	- `scoping-*` — Feature scoping, trade-offs, MVP definition
25	- `release-*` — Release planning, coordination, communication
26	- `metrics-*` — Product metrics, OKRs, success measurement
27	- `debt-*` — Technical debt management and balancing
28
29	## Core Frameworks
30
31	### The Product Trio
32
33	```
34	┌─────────────────┐
35	│ Product │
36	│ Manager │
37	└────────┬────────┘
38	│
39	┌─────────────┼─────────────┐
40	│ │ │
41	▼ ▼ ▼
42	┌────────┐ ┌──────────┐ ┌──────────┐
43	│ UX │ │Engineering│ │ Data │
44	│Designer│ │ Lead │ │ Analyst │
45	└────────┘ └──────────┘ └──────────┘
46	```
47
48	### Prioritization Framework Comparison
49
50	\| Framework \| Best For \| Scoring \| Complexity \|
51	\|-----------\|----------\|---------\|------------\|
52	\| RICE \| Feature prioritization \| Reach × Impact × Confidence / Effort \| Medium \|
53	\| ICE \| Quick decisions \| Impact × Confidence × Ease \| Low \|
54	\| MoSCoW \| Release scoping \| Must/Should/Could/Won't \| Low \|
55	\| Kano \| Customer satisfaction \| Delight/Performance/Basic \| High \|
56	\| Value vs Effort \| Quick 2x2 plotting \| Qualitative quadrants \| Low \|
57
58	### The Product Development Loop
59
60	```
61	┌──────────────────────────────────────────────────┐
62	│ │
63	│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
64	│ │ Discover │───▶│ Define │───▶│ Develop │ │
65	│ └──────────┘ └──────────┘ └──────────┘ │
66	│ ▲ │ │
67	│ │ ┌──────────┐ │ │
68	│ └─────────│ Measure │◀─────────┘ │
69	│ └──────────┘ │
70	│ │
71	└──────────────────────────────────────────────────┘
72	```
73
74	### Roadmap Types
75
76	\| Type \| Audience \| Time Horizon \| Detail Level \|
77	\|------\|----------\|--------------\|--------------\|
78	\| Vision \| Board, investors \| 2-5 years \| High-level themes \|
79	\| Strategic \| Leadership \| 1 year \| Quarterly goals \|
80	\| Release \| Stakeholders \| Quarter \| Features/epics \|
81	\| Sprint \| Dev team \| 2 weeks \| Stories/tasks \|
82
83	### The PM Decision Matrix
84
85	```
86	High Confidence
87	│
88	┌───────────────┼───────────────┐
89	│ VALIDATE │ SHIP │
90	│ (test more) │ (execute) │
91	Low │ │ │ High
92	Impact───┼───────────────┼───────────────┼───Impact
93	│ IGNORE │ INVESTIGATE │
94	│ (say no) │ (research) │
95	└───────────────┼───────────────┘
96	│
97	Low Confidence
98	```
99
100	## Stakeholder Map
101
102	\| Stakeholder \| Primary Interest \| Communication Style \|
103	\|-------------\|------------------\|---------------------\|
104	\| Executives \| Business outcomes, strategy \| High-level, metrics-focused \|
105	\| Engineering \| Technical feasibility, quality \| Detailed, collaborative \|
106	\| Design \| User experience, usability \| Visual, user-centric \|
107	\| Sales \| Revenue, competitive advantage \| Customer stories, timelines \|
108	\| Marketing \| Positioning, launch timing \| Messaging, dates \|
109	\| Support \| User satisfaction, volume \| Pain points, frequency \|
110	\| Customers \| Problems solved, value \| Empathy, listening \|
111
112	## Anti-Patterns
113
114	- Feature factory — Shipping without measuring outcomes
115	- Roadmap theater — Treating roadmaps as promises, not hypotheses
116	- Stakeholder-driven development — Building what's loudest, not what matters
117	- **Scope creep ac

People who liked this also viewed

6 picks

Type

product-manager

213installs3forks

View on GitHub

How to install product-manager?

ncklrs/startup-os-skills/product-manager

$npx -y skills add ncklrs/startup-os-skills --skill product-manager

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Product Manager
2
3	Strategic product management expertise for building the right things, in the right order, with the right people.
4
5	## Philosophy
6
7	Great product management isn't about features. It's about outcomes — solving real problems for real users in ways that drive business results.
8
9	The best product managers:
10	1. Obsess over problems, not solutions — Understand deeply before building
11	2. Say no more than yes — Focus is a feature
12	3. Bridge all worlds — Connect customers, engineering, design, and business
13	4. Make decisions reversible — Ship fast, learn faster
14	5. Own outcomes, not outputs — Features shipped means nothing without impact
15
16	## How This Skill Works
17
18	When invoked, apply the guidelines in `rules/` organized by:
19
20	- `roadmap-*` — Roadmap creation, maintenance, and communication
21	- `prioritization-*` — RICE, ICE, MoSCoW, and prioritization frameworks
22	- `stakeholder-*` — Managing up, down, and across the organization
23	- `sprint-*` — Sprint planning, backlog grooming, ceremonies
24	- `scoping-*` — Feature scoping, trade-offs, MVP definition
25	- `release-*` — Release planning, coordination, communication
26	- `metrics-*` — Product metrics, OKRs, success measurement
27	- `debt-*` — Technical debt management and balancing
28
29	## Core Frameworks
30
31	### The Product Trio
32
33	```
34	┌─────────────────┐
35	│ Product │
36	│ Manager │
37	└────────┬────────┘
38	│
39	┌─────────────┼─────────────┐
40	│ │ │
41	▼ ▼ ▼
42	┌────────┐ ┌──────────┐ ┌──────────┐
43	│ UX │ │Engineering│ │ Data │
44	│Designer│ │ Lead │ │ Analyst │
45	└────────┘ └──────────┘ └──────────┘
46	```
47
48	### Prioritization Framework Comparison
49
50	\| Framework \| Best For \| Scoring \| Complexity \|
51	\|-----------\|----------\|---------\|------------\|
52	\| RICE \| Feature prioritization \| Reach × Impact × Confidence / Effort \| Medium \|
53	\| ICE \| Quick decisions \| Impact × Confidence × Ease \| Low \|
54	\| MoSCoW \| Release scoping \| Must/Should/Could/Won't \| Low \|
55	\| Kano \| Customer satisfaction \| Delight/Performance/Basic \| High \|
56	\| Value vs Effort \| Quick 2x2 plotting \| Qualitative quadrants \| Low \|
57
58	### The Product Development Loop
59
60	```
61	┌──────────────────────────────────────────────────┐
62	│ │
63	│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
64	│ │ Discover │───▶│ Define │───▶│ Develop │ │
65	│ └──────────┘ └──────────┘ └──────────┘ │
66	│ ▲ │ │
67	│ │ ┌──────────┐ │ │
68	│ └─────────│ Measure │◀─────────┘ │
69	│ └──────────┘ │
70	│ │
71	└──────────────────────────────────────────────────┘
72	```
73
74	### Roadmap Types
75
76	\| Type \| Audience \| Time Horizon \| Detail Level \|
77	\|------\|----------\|--------------\|--------------\|
78	\| Vision \| Board, investors \| 2-5 years \| High-level themes \|
79	\| Strategic \| Leadership \| 1 year \| Quarterly goals \|
80	\| Release \| Stakeholders \| Quarter \| Features/epics \|
81	\| Sprint \| Dev team \| 2 weeks \| Stories/tasks \|
82
83	### The PM Decision Matrix
84
85	```
86	High Confidence
87	│
88	┌───────────────┼───────────────┐
89	│ VALIDATE │ SHIP │
90	│ (test more) │ (execute) │
91	Low │ │ │ High
92	Impact───┼───────────────┼───────────────┼───Impact
93	│ IGNORE │ INVESTIGATE │
94	│ (say no) │ (research) │
95	└───────────────┼───────────────┘
96	│
97	Low Confidence
98	```
99
100	## Stakeholder Map
101
102	\| Stakeholder \| Primary Interest \| Communication Style \|
103	\|-------------\|------------------\|---------------------\|
104	\| Executives \| Business outcomes, strategy \| High-level, metrics-focused \|
105	\| Engineering \| Technical feasibility, quality \| Detailed, collaborative \|
106	\| Design \| User experience, usability \| Visual, user-centric \|
107	\| Sales \| Revenue, competitive advantage \| Customer stories, timelines \|
108	\| Marketing \| Positioning, launch timing \| Messaging, dates \|
109	\| Support \| User satisfaction, volume \| Pain points, frequency \|
110	\| Customers \| Problems solved, value \| Empathy, listening \|
111
112	## Anti-Patterns
113
114	- Feature factory — Shipping without measuring outcomes
115	- Roadmap theater — Treating roadmaps as promises, not hypotheses
116	- Stakeholder-driven development — Building what's loudest, not what matters
117	- **Scope creep ac

People who liked this also viewed

6 picks

Type