pm-spec

Original：🇺🇸 English

Translated

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 "需求文档".

6installs

Sourcenexu-io/open-design

Added on2026-04-29

NPX Install

npx skill4agent add nexu-io/open-design pm-spec

SKILL.md Content

View Translation Comparison →

Product Spec Skill

Produce a one-page product spec / PRD.

Workflow

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.

Output contract

<artifact identifier="spec-name" type="text/html" title="Spec Title">
<!doctype html>...</artifact>