pm-spec
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 "需求文档".
npx skills add nexu-io/open-design --skill pm-spec --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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> ```
- Workflow
- Output contract
What does the pm-spec skill do?
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 "需求文档".
How do I install it?
Run `npx skills add nexu-io/open-design --skill pm-spec --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.