Product Spec Critic
Use this skill to find what a spec leaves unsaid. Optimize for clearer decisions, safer implementation handoff, and fewer avoidable surprises during build and launch.
Review Workflow
- Identify the user, problem, desired behavior, and product goal.
- Separate what the spec defines from what it implies.
- Look for ambiguity, omissions, edge cases, and contradictions.
- Check whether success metrics, rollout logic, and non-goals are explicit.
- Evaluate whether engineering, design, and product would make the same interpretation.
- Return findings first, then proposed fixes.
What To Check
Always inspect for:
- unclear user or target segment
- weak problem statement
- vague feature behavior
- missing scope boundaries
- missing non-goals
- edge cases and failure states
- permissions, trust, privacy, or abuse concerns
- data dependencies and source-of-truth confusion
- missing instrumentation or launch metrics
- rollout, fallback, and support implications
- handoff gaps likely to cause engineering rework
Output Shape
Lead with findings, ordered by severity.
For each finding, include:
- issue
- why it matters
- what should be added or changed
After findings, include:
- open questions
- assumptions you made
- revised spec outline, if useful
If the spec is strong, say so explicitly and then name any remaining risks or testing gaps.
Critique Rules
- Do not praise a spec into false confidence.
- Prefer precise criticism over broad "needs more detail" feedback.
- Focus on product risk, behavioral ambiguity, and launch risk.
- Call out when a spec is good for a prototype but not for production.
- Distinguish missing decisions from missing writing.
- Recommend the smallest clarifying additions that materially reduce confusion.
1---2name: product-spec-critic3description: Critical review skill for PRDs, feature specs, product plans, launch briefs, feature requests, wireframe notes, and implementation proposals. Use when Codex should pressure-test a product spec for ambiguity, missing requirements, edge cases, metrics, sequencing, UX risk, technical handoff quality, or launch-readiness gaps.4---56# Product Spec Critic78Use this skill to find what a spec leaves unsaid. Optimize for clearer decisions, safer implementation handoff, and fewer avoidable surprises during build and launch.910## Review Workflow11121. Identify the user, problem, desired behavior, and product goal.132. Separate what the spec defines from what it implies.143. Look for ambiguity, omissions, edge cases, and contradictions.154. Check whether success metrics, rollout logic, and non-goals are explicit.165. Evaluate whether engineering, design, and product would make the same interpretation.176. Return findings first, then proposed fixes.1819## What To Check2021Always inspect for:2223- unclear user or target segment24- weak problem statement25- vague feature behavior26- missing scope boundaries27- missing non-goals28- edge cases and failure states29- permissions, trust, privacy, or abuse concerns30- data dependencies and source-of-truth confusion31- missing instrumentation or launch metrics32- rollout, fallback, and support implications33- handoff gaps likely to cause engineering rework3435## Output Shape3637Lead with findings, ordered by severity.3839For each finding, include:4041- issue42- why it matters43- what should be added or changed4445After findings, include:4647- open questions48- assumptions you made49- revised spec outline, if useful5051If the spec is strong, say so explicitly and then name any remaining risks or testing gaps.5253## Critique Rules5455- Do not praise a spec into false confidence.56- Prefer precise criticism over broad "needs more detail" feedback.57- Focus on product risk, behavioral ambiguity, and launch risk.58- Call out when a spec is good for a prototype but not for production.59- Distinguish missing decisions from missing writing.60- Recommend the smallest clarifying additions that materially reduce confusion.
cnoles1980