pm-spec

Name: pm-spec
Availability: InStock
Author: az9713

Generate a one-page product spec from DESIGN.md briefs.

Updated May 2, 2026

Search Tags:#workflow #spec #product #prd #stakeholders #design-doc

Ready to run

npx skills add https://github.com/az9713/open-design-tutorial --skill pm-spec-az9713

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/az9713/open-design-tutorial/tree/main/skills/pm-spec
Command: npx skills add https://github.com/az9713/open-design-tutorial --skill pm-spec-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often need a concise, single-page PRD to align design, engineering, and product stakeholders from ideation to rollout.

Core Features & Use Cases

Generate a one-page product spec / PRD that clearly captures problem, goals, scope, user stories, rollout plan, and open questions.
Enforce a consistent structure with a header (title, status, date, owner), a three-line summary, and clearly separated sections for quick reference.
Support reuse across feature briefs, planning sessions, and design reviews to maintain alignment across teams.

Quick Start

Read the active DESIGN.md and generate a one-page PRD with sections for problem, goals, scope, user stories, milestones, and open questions.

Frequently Asked Questions about pm-spec

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

FAQPage Schema

How do I generate a one-page product spec from a design brief?▼

To generate a one-page product spec, the Skill extracts the problem, goals, scope, user stories, milestones, and open questions from your design brief and outputs a standardized, concise PRD artifact.

What sections should a concise PRD include for stakeholder alignment?▼

A concise PRD for stakeholder alignment should include a header with title, status, date, and owner, a three-line summary, and separated sections for problem, goals, scope, user stories, milestones, and open questions.

Can I create a standardized PRD from a DESIGN.md file for feature rollouts?▼

Yes, you can create a standardized PRD by reading your active DESIGN.md file; the Skill processes design notes and rollout plans to produce a consistent, single-page product spec.

Does this PRD generation approach work for planning sessions and design reviews?▼

This PRD generation approach works for planning sessions and design reviews by enforcing a consistent structure that captures problem, goals, scope, user stories, rollout plans, and open questions for team reuse.

What is the best way to document user stories and open questions for product teams?▼

The best way to document user stories and open questions is extracting them directly from design briefs into a standardized one-page product spec, maintaining clear separation for quick stakeholder reference.