| name | prd |
| aliases | ["/prd","product requirements","acceptance criteria"] |
| primaryRole | analyst |
| description | Transform a request into a measurable PRD with acceptance criteria, non-goals, and constraints. Use when a request needs a locked definition of done. |
PRD Skill (oh-my-antigravity)
Quick Start
- Write the objective, acceptance criteria, non-goals, constraints, and verification before execution begins.
Convert vague objectives into precise, locked product requirements.
Quick Start
- Starting a new feature or significant change
- The team needs clear "done" criteria before execution
- Scope creep is a risk and boundaries must be explicit
Workflow
- Capture objective: What are we building and why?
- Define acceptance criteria: Testable conditions for "done"
- List non-goals: What is explicitly out of scope
- Identify constraints: Technical, timeline, resource limits
- Specify verification: How we prove each criterion is met
- Lock: PRD becomes immutable until explicitly unlocked
PRD Template
## Objective
[1-2 sentences]
## Acceptance Criteria
- [ ] [Testable condition with measurable outcome]
- [ ] [Testable condition with measurable outcome]
## Non-Goals
- [Related thing that is NOT part of this work]
## Constraints
- [Technical/timeline/resource limitation]
## Risk Factors
- [What could block or derail this work]
## Verification Method
- [How each acceptance criterion will be verified]
Rules
- Every acceptance criterion must be independently testable
- Non-goals are mandatory — minimum 2 items
- Constraints must reference concrete limits (not "be fast")
- Once locked, changes require explicit unlock + re-approval
- PRD persisted to
.omg/state/prd.md
Related commands
/omg:team/prd — team-scoped PRD creation/omg:taskboard sync — generate tasks from PRD criteria
