Product Spec Skill
SkillDocs & knowledgepm-spec is a skill that guides an AI agent to write a one-page product spec / PRD from a feature brief. It identifies the feature and audience, then lays out standard PRD sections, problem, goals and non-goals, success metrics, user stories, scope milestones, and open questions, as a styled HTML document.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a feature brief that mentions PRD, spec, product spec, feature brief, or 需求文档 so the skill triggers.
Then ask your AI: use the Product Spec Skill skill
What your AI can do with it
- Identifies the feature and audience from the brief
- Writes a three-line summary covering what, who, and why now
- Drafts a problem panel with a customer or internal partner quote
- Builds a goals and non-goals two-column block
- Creates a success metrics table with metric, target, and measurement
- Lists user stories in as-a / I-want / so-that format with a scope milestone tracker
Getting started
- Have a feature brief that mentions PRD, spec, product spec, feature brief, or 需求文档 so the skill triggers.
- Have an active DESIGN.md file with color, typography, layout, and components sections, since the output uses it as a design system.
- Ask the agent to write the spec, optionally describing the problem, scope, milestones, and open questions you want covered.
- Receive the result as a styled single-page HTML artifact with a status pill, date, and owner in the header.
What this skill tells your AI
The instructions your AI receives, as published by nexu-io/open-design in design-templates/pm-spec/SKILL.md and read by ahel’s review.
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>
Signals
- GitHub stars
- 98k
- Forks
- 11k
- Last commit
- Sep 2026
Others that do the same job
Questions
- What does the output look like?
- A single-page HTML document with a header strip (title, status pill showing Draft, Review, or Approved, date, owner), a three-line summary, and panels for problem, goals, metrics, user stories, scope, and open questions.
- When should the skill be used?
- When the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".
- Does it need a design system?
- Yes. The skill reads the active DESIGN.md and requires sections for color, typography, layout, and components to style the output.
Advanced
- Item type
- skill
- Key
pm-spec-2- Source
- github.com/nexu-io/open-design