Product Management skills for Codex
Skills for the product side of building software: PRDs engineers can build from, user stories with acceptance criteria, outcome roadmaps and OKRs, honest prioritization, metric trees, customer interviews and jobs-to-be-done, MVP scoping, tracking plans and go-to-market plans.
curl -fsSL codexskills.dev/install.sh | sh -s -- --category product Installs all 20 into ~/.agents/skills/. Or download the zip.
All 20 Product Management skills
Each opens the full SKILL.md, example prompts and every way to install it.
-
Acceptance Criteria
Given/When/Then that testers cannot argue over -
Analytics Tracking Plan
One event taxonomy, enforced in code -
Beta Programs
Betas with exit criteria, not endless soft launches -
Competitive Teardown
Same task, both products, every claim sourced -
Customer Interviews
Ask about last Tuesday, not someday -
Feature Specs
One page with every state decided -
Feedback Triage
Turn feature requests into ranked customer problems -
Go-to-Market Plan
Launch sized to the change, every task owned -
Jobs to Be Done
Find the progress customers hire you for -
MVP Scoping
Test the assumption that could kill it, nothing more -
OKR Writing
Key results that measure outcomes, not to-do lists -
PRD Writing
Requirements an engineer can estimate on first read -
Pricing Strategy
Price on the value metric, backed by WTP data -
Prioritization Frameworks
RICE, WSJF and Kano scores you can defend -
Product Discovery
Test the riskiest assumption before writing code -
Product Metrics
A north star, a metric tree and unarguable definitions -
Roadmap Planning
Problems and metrics on the roadmap, not feature dates -
Sprint Planning
Commit to the low end of real velocity -
User Research Synthesis
Insights traceable to the people who said them -
User Stories
Thin vertical slices a team can finish in a sprint
No Product Management skill matches that.
Where to start
Install the ones that match requests you make every week. Name one with $prd-writing when you want it for sure; otherwise Codex picks by description.
Start with
- PRD WritingRequirements an engineer can estimate on first read
- Acceptance CriteriaGiven/When/Then that testers cannot argue over
- Analytics Tracking PlanOne event taxonomy, enforced in code
Install a few by name
curl -fsSL codexskills.dev/install.sh | sh -s -- acceptance-criteria analytics-tracking-plan 104-line POSIX script. No sudo, no telemetry. Read install.sh
In collections
Product Management FAQ
How do I install every Product Management skill at once?
Run curl -fsSL https://codexskills.dev/install.sh | sh -s -- --category product to put all 20 in ~/.agents/skills/, or add --project to install them into the current repository's .agents/skills/. You can also download the category zip and unpack it yourself.
Does installing 20 skills slow Codex down?
Hardly. At startup Codex sees only each skill's name and description, a few dozen words apiece, and reads a full SKILL.md only when a task needs it. Install the whole category if the work fits; unused skills cost almost nothing.
Which Product Management skill should I start with?
Start with PRD Writing, Acceptance Criteria, Analytics Tracking Plan. They cover the requests that come up most in this category. Mention one with $prd-writing to try it.