skills.rest
junainfinity
junainfinityCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pm-spec

Generate a one-page product spec from a design brief or DESIGN.md.

Updated Aug 27, 2026
Search Tags:#workflow#prd#user-stories#stakeholders#product-spec#design-brief#one-page-prd
One-click install
npx skills add https://github.com/junainfinity/osmDesign --skill pm-spec-junainfinity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/junainfinity/osmDesign/tree/main/skills/pm-spec
Command: npx skills add https://github.com/junainfinity/osmDesign --skill pm-spec-junainfinity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often draft lengthy PRDs and scattered notes that delay alignment and decision-making. This Skill automates turning a design brief or DESIGN.md into a single, shareable product spec.

Core Features & Use Cases

  • Generates a structured one-page PRD from a design brief, capturing problem, goals, scope, milestones, and questions.
  • Produces sections for user stories, success metrics, rollout plan, and open questions to align stakeholders.
  • Outputs an HTML artifact that can be embedded in documentation or shared with teams, with a readable header and clear sections.

Quick Start

Provide a concise feature brief and seed content; output a complete one-page PRD.

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 PRD from a design brief?▼

To generate a one-page PRD from a design brief, provide your concise feature proposal or seed content. The tool processes it into a structured product spec featuring problem statements, goals, user stories, and rollout milestones.

What sections should a one-page product spec include for stakeholder alignment?▼

A one-page product spec for stakeholder alignment should include sections for the problem, goals, non-goals, success metrics, user stories, rollout milestones, and open questions. This structure replaces lengthy PRDs with a single shareable document.

Can I turn an existing DESIGN.md file into a structured product spec?▼

Yes, you can turn an active DESIGN.md file into a structured product spec. The tool reads your design brief or DESIGN.md and outputs a structured spec with defined scope milestones and success metrics.

What is the best way to share a one-page PRD with my team?▼

The best way to share a one-page PRD is through the generated HTML artifact block. This output includes an inline style, header strip, and clearly defined panels, allowing it to be easily embedded in team documentation.

Does this tool work for feature proposals and rollout plans?▼

Yes, this tool works for feature proposals and rollout plans. It takes your brief and produces a structured spec complete with rollout milestones, success metrics, and open questions to align stakeholders.

Why use a one-page PRD instead of a lengthy product spec?▼

You should use a one-page PRD instead of a lengthy product spec because lengthy drafts and scattered notes delay decision-making. A single-page format automates alignment by capturing only essential problem, goals, and scope details.

Related Skills

Explore More Product & Management Skills→
az9713az9713

pm-spec

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

Community
Advanced
X-School-AcademyX-School-Academy
9

dev-swarm-mvp

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

Official
Basic
nexu-ionexu-io
84.7k

pm-spec

Generates a one-page HTML-ready product spec (PRD) with all required sections.

Official
Advanced
radenadriradenadri

write-prd

Draft structured PRDs from product ideas with goals, users, and metrics.

Community
Advanced