| name |
pm-spec |
| description |
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 |
platform |
scenario |
preview |
design_system |
example_prompt |
prototype |
desktop |
product |
| type |
entry |
html |
index.html |
|
| requires |
sections |
true |
color |
typography |
layout |
components |
|
|
Write me a PRD for adding two-factor auth to our SaaS app — problem, scope, milestones, open questions. |
|
Produce a one-page product spec / PRD.
- Read the active DESIGN.md.
- Identify the feature + audience from the brief.
- 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.
- One inline
<style>, semantic HTML, accent used twice max.
<artifact identifier="spec-name" type="text/html" title="Spec Title">
<!doctype html>...</artifact>