| name | pm-spec |
| description | Product requirements document (PRD) with user stories, acceptance criteria,
wireframes, and release checklist. Use for "PRD", "spec", "requirements".
|
| triggers | ["prd","product spec","requirements","spec document","feature spec"] |
| df | {"mode":"document","platform":"desktop","scenario":"product","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":false}} |
PM Spec Skill
Produce a product requirements document.
Sections
- Header: feature name, author, date, status (draft/review/approved).
- Overview: 1-paragraph summary + 3–5 bullet goals.
- User stories: table — as a [role] I want [action] so that [benefit].
- Acceptance criteria: numbered list with ✓ checkboxes.
- Wireframes: placeholder blocks labeled "Mobile / Desktop / Edge case".
- Open questions: highlighted box.
- Release checklist: table — item | owner | status.
- Appendix: related docs, metrics, rollback plan.
Rules
- Clean, scannable. Hierarchy via heading size, not color.
- Wireframes: gray placeholder blocks with labels, not detailed mockups.
data-df-id on each section.
Output
Single index.html, inline CSS.
