ahel
Start free

Product Spec Skill

SkillDocs & knowledge

pm-spec is a skill that turns a feature idea into a one-page product spec. It guides the agent to identify the feature and audience from your brief, then lay out standard PRD sections such as problem statement, goals and non-goals, success metrics, user stories, scope milestones, and open questions. The result is a styled HTML document using an existing design system file.

Use Product Spec Skill in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Product Spec Skill and connect your AI. About a minute.

ClaudeChatGPTAhel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Product Spec Skill skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Have a feature brief or idea ready to describe.

Product Spec SkillStart free

What your AI can do with it

  • Write a one-page product spec from a feature brief
  • Cover problem, goals, metrics, user stories, and rollout
  • Include scope milestones and open questions
  • Output the spec as a styled HTML document
  • Use an existing design system file for styling

Getting started

  1. Have a feature brief or idea ready to describe.
  2. Make sure the skill is available to your agent.
  3. Provide the brief and any design system file to use.
  4. Ask the agent to produce the product spec.

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

  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>

Signals

GitHub stars
99k
Forks
11k
Last commit
Oct 2026

Others that do the same job

pm-spec
Skill · mphinance

Questions

What sections does the spec include?
Problem statement, goals and non-goals, success metrics, user stories, scope milestones, design notes, rollout plan, and open questions.
What format is the output?
A styled HTML document that uses an existing design system file.
When should I use this skill?
Use it when your brief mentions PRD, spec, product spec, feature brief, or 需求文档.
Does it need a design system file?
Yes, the output uses an existing design system file for styling.
Advanced
Item type
skill
Key
pm-spec-2
Source
github.com/nexu-io/open-design

github.com/nexu-io/open-design

More in Docs & knowledge

handoff
Skill · mattpocock
More in Docs & knowledgecanvas-design
Skill · anthropics
More in Docs & knowledgedoc-coauthoring
Skill · anthropics
More in Docs & knowledgewriting-for-agents
Skill · mattpocock
More in Docs & knowledgespec-driven-development
Skill · addyosmani
More in Docs & knowledgedefuddle
Skill · kepano
More in Docs & knowledge