pm-spec

Guide users through creating product specifications with structured PRD sections.

Updated May 11, 2026
One-click install
npx skills add https://github.com/Maccio-huang/opendesign --skill pm-spec-maccio-huang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/Maccio-huang/opendesign/tree/main/skills/pm-spec
Command: npx skills add https://github.com/Maccio-huang/opendesign --skill pm-spec-maccio-huang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured framework for creating detailed product specifications (PRD), ensuring all necessary components are covered in a single document.

Core Features & Use Cases

  • Comprehensive Structure: Guides the creation of sections like problem, goals, success metrics, user stories, and rollout milestones.
  • Customizable Design: Allows for the use of a specified design system with sections like color, typography, layout, and components.
  • Use Case: When developing a new feature for a SaaS app, use this Skill to create a PRD that outlines the problem, scope, and success metrics, ensuring all stakeholders are aligned.

Quick Start

Generate a product spec for the 'two-factor authentication' feature using the pm-spec skill.

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 product specification for a new SaaS feature?

A comprehensive product specification framework guides you through defining the problem, scope, goals, success metrics, user stories, and rollout milestones to ensure all stakeholders are aligned on the feature.

What sections should be included in a PRD for product development?

A PRD should include sections for the problem statement, goals, success metrics, user stories, rollout milestones, and optionally a design system covering color, typography, layout, and components.

Can I align my feature documentation with a specific design system?

Yes, you can align your feature documentation with a design system by customizing the PRD to include sections for color, typography, layout, and components to ensure design consistency.

What is the best way to document success metrics in a product spec?

The best way to document success metrics in a product spec is to use a structured framework that requires you to explicitly define these metrics alongside the problem statement and scope during the creation process.

Do I need any specific tools to generate feature specifications using this approach?

No specific tools are required to generate feature specifications using this approach, as it relies on scripts and reference components to guide the documentation process without external dependencies.