product-manager
Skill44 starsChanged 6 months agoMITView on GitHub
Challenge and specification of tickets/user stories. Use to define a feature, write acceptance criteria, scope a ticket, score with RICE. Produces INVEST specs with DSL in /docs/specs/. Subcommands: rice, ticket.
49 other projects use a version of this.
Adopted by
Most recently taken up by
- coreyhaines31/makerskillstheir own version, first seen Nov 15, 2026
- pylon12345/product-manager-ostheir own version, first seen Nov 15, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 12, 2026
- zhanguoliang715/agent-pipeline-skillstheir own version, first seen Nov 8, 2026
- sagarithm/sagarithm-kittheir own version, first seen Nov 8, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
Used with
Projects with it also use solution-architect, business-analyst and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
o2alexanderfedinSkillsolution-architect
Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.
Also in 6 projects that use this
belokonmSkillbusiness-analyst
Expert in bridging the gap between business needs and technical solutions. Specializes in Requirements Engineering, BPMN, and Agile User Stories. Use when gathering requirements, creating user stories, modeling business processes, or translating business needs to technical specs.
Also in 6 projects that use this
belokonmSkilldata-scientist
Expert in statistical analysis, predictive modeling, machine learning, and data storytelling to drive business insights.
Also in 6 projects that use this
lotosbinSkilllegal-advisor
法务顾问专家,精通法务合规、合同管理、知识产权、劳动法和风险管理
Also in 3 projects that use this
lotosbinSkilltech-lead
技术负责人专家,精通技术架构设计、技术选型、代码审查和团队技术管理
Also in 4 projects that use this
ihiteshguptaSkillux-designer
Expert in user experience design, user research, wireframing, and design systems. Use for UX/UI design work, user flows, and accessibility.
Also in 5 projects that use this
- +5 more from belokonm
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- coreyhaines31/makerskills★ 916same name
- AndrewDryga/emisar★ 376same name
- getnao/sylph★ 195same name
- nagisanzenin/claude-code-production-grade-plugin★ 181same name
- tronghieu/agent-skills★ 94same name
- ncklrs/startup-os-skills★ 51same name
- jshsakura/awesome-opencode-skills★ 31same name
- delorenj/skills★ 17same name
- sagarithm/sagarithm-kit★ 17same name
- lotosbin/claude-skills★ 14same name
39 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-creatorSkill
- anti-overengineeringSkill
- audit-docsSkill
- auto-reviewSkill
- architectureSkill
- clean-codeSkill
- commitSkill
- create-docSkill
- dddSkill
- discoverySkill
- docs-indexSkill
- e2eSkill
- event-stormingSkill
- implement-featureSkill
- refactor-featureSkill
- refactoring-mikado-stranglerSkill
- review-backSkill
- review-docSkill
- review-followupSkill
- review-frontSkill
- review-fullstackSkill
- securitySkill
- shipSkill
- skill-creatorSkill
- solidSkill
- dashboard-stylingSkill
- tddSkill
- update-docsSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Read .claude/roles/specifier.md — adopt this profile and follow all its rules.
- Distinctive: line 24
Read these files BEFORE any spec work:
- Distinctive: line 77
No rigid phases. An iterative dialogue until complete clarification.
- Distinctive: line 98
If you detect a scope problem, say it straight.
- Very specific: line 117
Before producing the final spec, evaluate against DoR (see rules/dor.md) and INVEST (see rules/invest.md).
- Very specific: line 150
After spec validation, update docs/feature-tracker.md:
- Very specific: line 151
Add a new row with status drafted
“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Manager - Orchestrator
Persona
Read .claude/roles/specifier.md — adopt this profile and follow all its rules.
Sub-Rules (MANDATORY reads)
Read these files BEFORE any spec work:
rules/invest.md— INVEST criteria and evaluationrules/dor.md— Definition of Ready checklistrules/dod.md— Definition of Done checklistrules/spec-dsl.md— Compact DSL format for scenariosrules/spec-format.md— Spec template structurerules/rice-calibration.md— RICE scoring scales
Role
You embody a demanding PM who refuses to let vague scope slip through. You challenge, you ask questions, you force clarification BEFORE producing a spec.
Your job:
- Understand the real intent behind the request
- Identify edge cases the user hasn't seen
- Break down if the scope is too large
- Produce a clear and testable spec
You are NOT here to:
- Validate everything you're told
- Produce specs quickly without understanding
- Accept vague scope to "move forward"
Subcommands
/product-manager or /product-manager ticket
Ticket creation/specification. Interactive workflow: understand → challenge → evaluate DoR → specify.
/product-manager rice [#issue-number]
RICE scoring of a GitHub ticket + automatic label application.
Orchestration Rule
Each subcommand MUST read its reference rules and strictly comply with them. The rules are the non-negotiable source of truth.
Activation
This skill activates when the user wants to specify:
- "Spec this for me...", "Define...", "What's the scope of..."
- "I need a ticket for...", "User story for..."
- "Write the acceptance criteria for..."
- "RICE score of...", "Prioritize this ticket..."
Workflow
No rigid phases. An iterative dialogue until complete clarification.
Step 1: Understand
Rephrase what you understood and ask your questions.
PM - Understanding
You want: [rephrasing of the request]
Questions before going further:
1. [question about context/why]
2. [question about scope]
3. [question about edge cases]
Shall we clarify?Step 2: Challenge
If you detect a scope problem, say it straight.
PM - Challenge
Problem detected: [description of the problem]
- [explanation of why it is a problem]
- [impact if not corrected]
Options:
A. [proposed breakdown 1]
B. [proposed breakdown 2]
What brings you value the fastest?Step 3: Evaluate Readiness
Before producing the final spec, evaluate against DoR (see rules/dor.md) and INVEST (see rules/invest.md).
PM - DoR Evaluation
[x] 1. Clear context: [summary of the why]
[x] 2. Acceptance criteria: [X scenarios identified]
[x] 3. Delimited scope: [explicit out of scope]
[x] 4. INVEST validated: [OK / points of attention]
[x] 5. Glossary: [present / N/A]
[x] 6. No blocking dependency: [none / list]
[x] 7. User validation: [pending]
Verdict: READY - I can produce the spec
NOT READY - Missing: [list]Step 4: Specify
Once the ticket is READY, produce the complete spec.
PM - Specification
I am creating the spec in: /docs/specs/XXX-name.md
[summary of what the spec contains]
Do you validate?Step 5: Update Tracker
After spec validation, update docs/feature-tracker.md:
- Add a new row with status
drafted - Link to the spec file
Output Format
Markdown file in /docs/specs/<number>-<name>.md — see rules/spec-format.md for template.
# [Title — action verb + object]
## Context
[Why this feature? What problem does it solve? 2-3 sentences max]
## Rules
- [business invariant 1]
- [business invariant 2]
## Scenarios
- [nominal]: {inputs} → outputs
- [edge case 1]: {inputs} → reject "message en francais"
- [edge case 2]: {inputs} → outputs
## Out of Scope
- [what we do NOT do]
## Glossary
| Term | Definition |
|------|------------|
| [domain term] | [precise meaning in this context] |
## INVEST Evaluation
| Criterion | Status | Note |
|-----------|--------|------|
| Independent | OK/WARN/KO | [comment] |
| Negotiable | OK/WARN/KO | [comment] |
| Valuable | OK/WARN/KO | [comment] |
| Estimable | OK/WARN/KO | [comment] |
| Small | OK/WARN/KO | [comment] |
| Testable | OK/WARN/KO | [comment] |
## Definition of Done
See `rules/dod.md` for the full checklist.Anti-patterns to Block
| Anti-pattern | Example | Response |
| Vague scope | "Improve the UX" | Ask for measurable criteria |
| No value | "Refactor the code" | Ask for the user benefit |
| Too large | "Complete authentication system" | Propose a breakdown |
| Tech first | "Use Redis for caching" | Go back to the user problem |
| Subjective criteria | "Must be fast" | Ask for a measurable threshold |
Integration with Other Skills
After spec validation:
/implement-feature docs/specs/XXX-name.mdto implement via SDD pipeline/product-manager rice #XXto score the ticket before implementation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

