pm-spec — Claude Code skill: what it does, how to install
pm-spec builds a one-page PRD with the problem, metrics, scope, user stories, design notes, rollout plan, and open questions.
Apache-2.0 234 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill pm-spec -a claude-codeWhat pm-spec does
This skill turns a short brief into a one-page product spec or PRD. It identifies the feature and audience, then lays out a summary, Problem panel, goals and non-goals, a success-metrics table, user stories, a phased scope tracker, and open questions.
The result is a semantic HTML artifact with one inline style and limited accent use. Its structure includes status, date, owner, design notes, and assignee chips; the output contract uses an artifact identifier and HTML type. The workflow starts by reading the active DESIGN.md, so that file needs to be ready first. The skill targets Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
What it helps with
- turn a feature brief into a PRD
- define the feature problem and audience
- separate goals from non-goals
- put success metrics into a target table
- map scope into rollout phases
Example prompts for the agent
- Write a PRD for adding two-factor authentication to our SaaS, covering the problem, scope, milestones, and open questions.
- Create a product spec for this feature with user stories, success metrics, and a rollout plan.
- Turn this brief into a one-page HTML product spec.
How to install pm-spec
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pm-spec -a claude-code2Manually: put the files in place
~/.claude/skills/pm-spec/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pm-spec/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pm-spec -a codex2Manually: put the files in place
.agents/skills/pm-spec/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pm-spec -a cursor2Manually: put the files in place
.cursor/skills/pm-spec/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/pm-spec/SKILL.md2Manually: put the files in place
.github/skills/pm-spec/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pm-spec -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/pm-specManually: put the files in place
.devin/skills/pm-spec/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill pm-spec -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pm-spec
How do I install pm-spec in Claude Code?
Run npx skills add nexu-io/open-design --skill pm-spec -a claude-code, then use ~/.claude/skills/pm-spec/SKILL.md.
What does pm-spec do?
It turns a product brief into a one-page PRD with the problem, goals, success metrics, user stories, scope, rollout phases, and open questions.
What does pm-spec need before it runs?
Its workflow begins by reading the active DESIGN.md. The result is a semantic HTML artifact with one inline style.
Source text
SKILL.md · Apache-2.0
---
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: 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>
```
© nexu-io · Apache-2.0 · nexu-io/open-design