Discovery synthesis
Organize interviews, support themes, analytics, research, requests, and competitive context into evidence and unanswered questions.
Codex Skills for Product Managers give Codex practical instructions for synthesizing customer evidence, framing problems, writing product requirements, prioritizing opportunities, planning roadmaps, defining metrics, and communicating decisions. Download the skills for product work that turns scattered input into choices a team can understand and test.
task: complete product management task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffStrong product management work depends on context, explicit decisions, and checks that match the real environment.
These skills give Codex a specialist workflow for product management while preserving local conventions, important constraints, and human review.
Organize interviews, support themes, analytics, research, requests, and competitive context into evidence and unanswered questions.
Write problem statements, user scenarios, scope, acceptance criteria, constraints, edge cases, dependencies, and non-goals.
Compare opportunities using strategy, customer value, evidence, effort, risk, sequencing, and expected outcomes.
Define success, guardrails, events, experiment plans, decision logs, stakeholder updates, and launch learning.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
State the product goal, target user, problem, evidence, strategic context, constraints, and deadline.
Synthesize sources, identify gaps, map risks, and decide what must be learned before committing.
Set outcome, scope, requirements, non-goals, dependencies, acceptance criteria, and measurement.
Communicate tradeoffs, track decisions, support implementation, prepare launch, and review results against expectations.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Plan interviews and experiments, synthesize evidence, map journeys, and reduce the riskiest assumptions.
Create briefs, user stories, acceptance criteria, edge cases, dependencies, and decision records.
Connect company goals, customer problems, opportunities, sequencing, resources, and product bets.
Coordinate readiness, positioning, support, analytics, rollout, feedback, and post-launch review.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable product management work with a visible process.
Turn customer, market, business, and technical information into clear product decisions.
Prepare backlog items, acceptance criteria, sequencing, dependencies, and delivery context.
Structure discovery, scope, priorities, launch choices, and learning without a large product team.
Create shared context across design, engineering, marketing, sales, support, data, and leadership.
The skills support product reasoning but do not replace customer contact, accountable prioritization, technical estimates, design research, legal review, or leadership decisions.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with the included product management guidance, checks, and supporting files.
Use project scope for local rules and versions, or personal scope for a reusable workflow.
Document the tools, audience, standards, source material, constraints, and approval rules for this product management work.
Provide the intended outcome, important edge cases, required checks, and expected handoff.
Practical answers about capabilities, limits, setup, and review.
Yes. They can create focused requirements documents from supplied evidence, constraints, technical context, and decision needs.
They can compare opportunities transparently, but leadership and product owners remain accountable for tradeoffs.
Yes. They can prepare research plans, synthesize interviews and data, map assumptions, and design learning steps.
Yes. They can connect outcomes to events, formulas, baselines, guardrails, segments, and review cadence.
No. They help plan and synthesize research, but direct evidence from customers and product use is essential.
Clear context. Purposeful work. Relevant checks. A result others can understand.