pm-spec
Create single-page product specs or PRDs covering problem, success metrics, scope, risks, and launch notes. Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".
Source facts
- Repository
- onfire7777/universal-ai-skills-library
- Last source activity
- May 10, 2026 at 01:21
- Detected SKILL.md language
- English
- Stars
- 16
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
File Explorer
3 filesShowing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- pm-spec
- description
- Create single-page product specs or PRDs covering problem, success metrics, scope, risks, and launch notes. Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".
- triggers
- ["prd","spec","product spec","feature brief","feature doc","需求文档"]
- od
- {"mode":"prototype","platform":"desktop","scenario":"product","preview":{"type":"html","entry":"index.html"},"design_system":{"requires":true,"sections":["color","typography","layout","components"]},"example_prompt":"Write me a PRD for adding two-factor auth to our SaaS app — problem, scope, milestones, open questions."}
# Product Spec Skill
Produce a one-page product spec / PRD.
## Workflow
1. Read the active DESIGN.md.
2. Identify the feature + audience from the brief.
3. Layout:
- Header strip: title, status pill (Draft / Review / Approved), date, owner.
- Three-line summary at the top — what, who, why now.
- "Problem" panel with one paragraph and a quote from a customer or
internal partner.
- "Goals & non-goals" two-column block.
- "Success metrics" table with metric / target / measurement.
- "User stories" list with as-a / I-want / so-that format.
- "Scope" milestone tracker (3–4 phases).
- "Open questions" with assignee chips.
4. One inline `<style>`, semantic HTML, accent used twice max.
## Output contract
```
<artifact identifier="spec-name" type="text/html" title="Spec Title">
<!doctype html>...</artifact>
```
View on GitHub