| name | product-planning |
| description | Use when product strategy, PRD creation, feature prioritization, opportunity analysis, acceptance criteria, or pre-mortem risk analysis is needed before implementation. |
Product Planning
This skill adapts product management workflows for Codex implementation work.
Use When
- The task needs a feature plan, PRD, or acceptance criteria.
- The user asks for strategy, scope, roadmap, prioritization, or product direction.
- A high-value coding task needs product clarity before implementation.
Non-Trigger
Do not use for purely mechanical code edits where the product outcome and acceptance criteria are already explicit.
Process
- Clarify the user problem and target segment.
- Define the desired outcome and success signals.
- Separate opportunities from solutions.
- Prioritize by impact, confidence, effort, risk, and time-to-learn.
- Draft implementation-ready acceptance criteria.
- Run a pre-mortem:
- Tigers: real risks that can derail the work.
- Paper Tigers: concerns that are likely overblown.
- Elephants: unspoken assumptions that need investigation.
- Hand off only the scope that is ready for engineering.
Output Contract
Return:
- problem statement
- target user or segment
- ship-now scope
- deferred scope
- acceptance criteria
- success metric
- risks and mitigations
- unresolved decisions