Skip to content
Skillpedia
Documentation101k · #492

pm-spec

Lets your agent create a complete product specification document. It includes the problem, metrics, scope, user stories, and design notes to guide development.

What it does

This tool creates a one-page product specification document (PRD). It organizes ideas about a new feature or product, explaining the problem it solves, who it helps, and how to measure its success.

When to use it

  • ✓When you need to detail a new product idea.
  • ✓When defining the goals and scope of a new feature.
  • ✓To communicate a product plan to your team.

Example of what to ask your AI

“Create a product spec for an app that helps people find hiking trails.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/nexu-io/open-design/blob/main/design-templates/pm-spec/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/nexu-io/open-design/blob/main/design-templates/pm-spec/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The AI reads your ideas and organizes them into standard sections like 'Problem,' 'Goals,' 'Success Metrics,' and 'User Stories.' It formats everything into a clear, concise HTML document.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add nexu-io/open-design --skill pm-spec

Or download just the file:

curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/design-templates/pm-spec/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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>
FAQ

What is a PRD?

PRD stands for Product Requirements Document. It's a document that outlines what a product should do and how it should function.

What information do I need to provide?

You need to provide context about the feature or product you want to specify, such as the problem it solves and who the users are.

What is the output format?

The output is a one-page HTML document that is easy to read and share.

Details

Original description by the author

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

repo: nexu-io/open-design

Popularity

GitHub stars
101k
Ranking position
#492
License
Apache-2.0
Updated
10/16/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills