Skip to main content
Agent skill

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

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Pm Spec when an AI agent needs a reusable SKILL.md workflow for this job: 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 "需求文档".

When not to use it

Skip Pm Spec when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/pm-spec
# Save SKILL.md to ~/.claude/skills/pm-spec/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/pm-spec/SKILL.md. For a shared project, commit the folder at .claude/skills/pm-spec/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Pm Spec skill for this task: Read the active DESIGN.md. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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> ```

Intended uses

  • 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
  • "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.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.