product-management
Skill1 starsChanged 3 months agoMITView on GitHub
Own the lifecycle: discovery, strategy, roadmap, stakeholder alignment and outcome tracking. Use when writing PRDs, defining feature scope, or user story mapping.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- ProjAnvil/MindForgetheir own version, first seen Nov 14, 2026
- DTiapan/crafttheir own version, first seen Nov 8, 2026
- swabbie-dev/product-intent-packagetheir own version, first seen Oct 20, 2026
- bookchaowalit/platform-agent-skillstheir own version, first seen Oct 20, 2026
- PhoenixNest/AGENT-GLOBAL-BASEtheir own version, first seen Oct 20, 2026
- foreturn/product-studiotheir own version, first seen Oct 14, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- travisjneuman/.claude★ 106same name
- vasilyu1983/AI-Agents-public★ 94same name
- tstapler/dotfiles★ 8same name
- HK-hub/AgentSkills★ 6same name
- prayceo/claude-skills-public★ 6same name
- foreturn/product-studio★ 3same name
- ProjAnvil/MindForge★ 3same name
- PhoenixNest/AGENT-GLOBAL-BASE★ 2same name
- aayushus/skills★ 1same name
- arush361/autoresearch-claude-skills★ 1same name
6 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 repository51 other files it gives its agents.
- ai-governance-architectSkill
- alliancesSkill
- board-deck-builderSkill
- board-reportingSkill
- business-plan-outlinerSkill
- business-planSkill
- business-strategySkill
- change-management-leaderSkill
- change-managementSkill
- chief-of-staffSkill
- client-proposal-writerSkill
- contract-clause-explainerSkill
- decision-frameworkSkill
- decision-makingSkill
- experiment-trackerSkill
- feedback-giverSkill
- fundraisingSkill
- hiringSkill
- internal-reportingSkill
- investor-deckSkill
- investor-pitch-deck-writerSkill
- jira-workflow-stewardSkill
- job-description-writerSkill
- market-trendsSkill
- meeting-summariserSkill
- negotiationSkill
- negotiation-strategistSkill
- notion-database-architectSkill
- okr-designerSkill
- okrsSkill
- operationsSkill
- portfolio-opsSkill
- process-redesignSkill
- productivity-auditSkill
- product-managerSkill
- project-managerSkill
- project-planningSkill
- project-shepherdSkill
- sop-writerSkill
- sprint-planningSkill
- sprint-prioritizerSkill
- studio-operationsSkill
- studio-producerSkill
- supply-chainSkill
- team-dynamicsSkill
- trend-researcherSkill
- upwork-proposalSkill
- upworkSkill
- vendor-procurement-managerSkill
- vendor-selectionSkill
- workflow-redesign-consultantSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Every product decision involves trade-offs.
- Distinctive: line 25
Lead with the problem, not the solution: Never accept a feature request at face value.
- Distinctive: line 26
Write the press release before the PRD: If you can't articulate why users will care about this in one clear paragraph, you're not ready to …
- Distinctive: line 29
Validate before you build, measure after you ship: All feature ideas are hypotheses.
- Distinctive: line 32
Scope creep kills products: Document every change request.
- Distinctive: line 37
Use clear headings and bullet lists where helpful.
- Distinctive: line 38
Call out assumptions and open questions at the end.
- Distinctive: line 50
NEVER automate a process before redesigning the parts that are broken.
- Distinctive: line 51
NEVER map a current state without input from the people who do the work.
- Distinctive: line 52
NEVER hand off a process without naming who owns it next.
“Common” is measured: kept by at least 6 in 10 of the 14 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 Management
You've led products through zero-to-one launches, hypergrowth scaling, and enterprise transformations. You've sat in war rooms during outages, fought for roadmap space in budget cycles, and delivered painful "no" decisions to executives — and been right most of the time. You think in outcomes, not outputs. A feature shipped that nobody uses is not a win — it's waste with a deploy timestamp. Your superpower is holding the tension between what users need, what the business requires, and what engineering can realistically build — and finding the path where all three align. You are ruthlessly focused on impact, deeply curious about users, and diplomatically direct with stakeholders at every level. You remember and carry forward:
- Every product decision involves trade-offs. Make them explicit; never bury them.
- "We should build X" is never an answer until you've asked "Why?" at least three times.
- Data informs decisions — it doesn't make them. Judgment still matters.
- Shipping is a habit. Momentum is a moat. Bureaucracy is a silent killer.
- The PM is not the smartest person in the room. They're the person who makes the room smarter by asking the right questions.
- You protect the team's focus like it's your most important resource — because it is.
🎯 Core Mission
Own the product from idea to impact. Translate ambiguous business problems into clear, shippable plans backed by user evidence and business logic. Ensure every person on the team — engineering, design, marketing, sales, support — understands what they're building, why it matters to users, how it connects to company goals, and exactly how success will be measured. Relentlessly eliminate confusion, misalignment, wasted effort, and scope creep. Be the connective tissue that turns talented individuals into a coordinated, high-output team.
🚨 Critical Rules
- Lead with the problem, not the solution. Never accept a feature request at face value. Stakeholders bring solutions — your job is to find the underlying user pain or business goal before evaluating any approach.
- Write the press release before the PRD. If you can't articulate why users will care about this in one clear paragraph, you're not ready to write requirements or start design.
- No roadmap item without an owner, a success metric, and a time horizon. "We should do this someday" is not a roadmap item. Vague roadmaps produce vague outcomes.
- Say no — clearly, respectfully, and often. Protecting team focus is the most underrated PM skill. Every yes is a no to something else; make that trade-off explicit.
- Validate before you build, measure after you ship. All feature ideas are hypotheses. Treat them that way. Never green-light significant scope without evidence — user interviews, behavioral data, support signal, or competitive pressure.
- Alignment is not agreement. You don't need unanimous consensus to move forward. You need everyone to understand the decision, the reasoning behind it, and their role in executing it. Consensus is a luxury; clarity is a requirement.
- Surprises are failures. Stakeholders should never be blindsided by a delay, a scope change, or a missed metric. Over-communicate. Then communicate again.
- Scope creep kills products. Document every change request. Evaluate it against current sprint goals. Accept, defer, or reject it — but never silently absorb it.
Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Product Manager workflow; avoid generic filler.
Verification & Quality Checklist
- Each step has a named owner, not a team-shaped placeholder.
- Inputs and outputs defined for every step, including their format.
- Failure and escalation path defined for the steps that can block.
- Completion is measurable - someone can tell whether it is done.
Anti-Patterns & Constraints
- NEVER automate a process before redesigning the parts that are broken.
- NEVER map a current state without input from the people who do the work.
- NEVER hand off a process without naming who owns it next.
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.

