skills.rest
MyHeavenDyf
MyHeavenDyfCOMMUNITY
Explore all skills by this author →
GitHub

pm-spec

Create product specification documents with structured sections for problem, goals, metrics, and user stories.

1|Updated May 8, 2026
Search Tags:#PRD#feature specification#product requirements#product spec#design notes
One-click install
npx skills add https://github.com/MyHeavenDyf/UXAI --skill pm-spec-myheavendyf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/MyHeavenDyf/UXAI/tree/main/packages/app/octoapp/templates/pm-spec
Command: npx skills add https://github.com/MyHeavenDyf/UXAI --skill pm-spec-myheavendyf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill generates a comprehensive product specification document, streamlining the process of writing and organizing product requirements and design notes.

Core Features & Use Cases

  • Single Page Creation: Compile all necessary information into a single, easily accessible document.
  • Customizable Templates: Customize the layout, including headers, summaries, problem statements, goals, success metrics, user stories, and more.
  • Use Case: When you need to quickly draft a PRD for a new feature, this Skill can help you get started with a well-structured document, saving time and reducing errors.

Quick Start

Generate a product spec for a new feature, "Two-Factor Authentication," with the problem statement, success metrics, and user stories.

Frequently Asked Questions about pm-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a single-page product spec for a new feature?▼

To create a single-page product spec, compile problem statements, goals, success metrics, user stories, and scope into a structured PRD using customizable templates. This process streamlines writing and organizing product requirements into an easily accessible document.

What sections should be included in a product requirements document?▼

A product requirements document should include headers, summaries, problem statements, goals, success metrics, user stories, and scope. These structured sections ensure comprehensive coverage of design notes and feature specifications.

Can I draft feature specifications and design notes without prior PRD knowledge?▼

Drafting feature specifications requires knowledge of the product domain and design system requirements. While the process streamlines writing, you need domain expertise to accurately define the problem, scope, and user stories.

What is the best way to structure a PRD for quick feature launches?▼

The best way to structure a PRD for quick launches is to use a single-page layout with predefined sections for success metrics and user stories. This reduces errors and saves time by organizing all requirements into one accessible document.

How does the web-based preview interface handle product spec generation?▼

The web-based preview interface operates within a desktop environment to display the generated product spec. It allows you to visualize the single-page document containing your structured problem statements, goals, and user stories.

Related Skills

Explore More Product & Management Skills→
sinositatosinositato

prd-discover

Gather problem, user, scope, and success criteria into a markdown context file.

Community
Intermediate
X-School-AcademyX-School-Academy
9

dev-swarm-mvp

Define MVP scope, success metrics, and acceptance criteria for early product validation.

Official
Basic
Ayushman-11Ayushman-11

ui-ux-designer

Create interface designs, wireframes, and design systems with design tokens.

Community
Advanced
Kushal9889Kushal9889

create-prd

Guide PRD creation from product, feature, and JTBD documentation.

Community
Intermediate