skills.rest
PiercingXX
PiercingXXCOMMUNITY
Explore all skills by this author →
GitHub

pm-spec

Convert product feature briefs into one-page HTML PRDs.

1|Updated Jul 9, 2026
Search Tags:#requirements#user stories#prd#success metrics#product spec#rollout plan
One-click install
npx skills add https://github.com/PiercingXX/xx-stack --skill pm-spec-piercingxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/PiercingXX/xx-stack/tree/main/packs/design/runtime/skills/design/pm-spec
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill pm-spec-piercingxx

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps you convert an ambiguous feature brief into a crisp, decision-ready product spec that aligns stakeholders on problem, goals, scope, and success metrics.

Core Features & Use Cases

  • Single-page PRD output: Produces a compact product spec covering problem, goals/non-goals, success metrics, user stories, scope milestones, and open questions.
  • Design-guided structure: Uses the active DESIGN.md to follow the required layout and visual system while keeping the output consistent and reviewable.
  • HTML artifact contract: Emits a self-contained HTML artifact suitable for preview and sharing with design and product stakeholders.

Quick Start

Use the pm-spec skill to generate a one-page PRD from the provided feature brief and related DESIGN.md context, producing a ready-to-review HTML spec artifact.

Frequently Asked Questions about pm-spec

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

FAQPage Schema
How do I turn a feature brief into a one-page PRD?▼

To turn a feature brief into a one-page PRD, provide the brief to the skill. It organizes the problem, success metrics, scope milestones, and user stories into a single decision-ready HTML artifact.

What is the best way to write a product spec for desktop web scenarios?▼

The best way to write a product spec for desktop web scenarios is using a structured PRD format. This skill converts briefs into aligned specs covering goals, non-goals, and rollout planning.

How do I structure success metrics and user stories into a single product spec?▼

Structure success metrics and user stories into a product spec by using a one-page PRD template. The skill automatically maps these elements alongside scope milestones and open questions.

Can I generate an HTML artifact for my PRD to share with design stakeholders?▼

Yes, you can generate an HTML artifact for your PRD to share with design stakeholders. The skill emits self-contained HTML wrapped in a specified artifact identifier contract for previewing.

Does the generated product spec include space for open questions and non-goals?▼

Yes, the generated product spec includes space for open questions and non-goals. The one-page PRD output explicitly covers goals, non-goals, success metrics, scope milestones, and open questions.

When do I need a request-for-spec workflow for product and rollout planning?▼

You need a request-for-spec workflow for product and rollout planning when you have an ambiguous feature brief. It helps align stakeholders on the problem, scope, and success metrics before development.

Related Skills

Explore More Product & Management Skills→
Gentleman-ProgrammingGentleman-Programming
618

skill-creator

Generate standardized SKILL.md files and templates for AI agent skills.

Official
Basic
pipixia-labspipixia-labs
38

pm-spec

Convert a design brief into a structured one-page product spec.

Official
Advanced
adorosarioadorosario
1

drafting-innovation-prd-one-pagers

Draft one-page PRDs for innovation projects from structured ideas.

Community
Basic
gaoqiongxiegaoqiongxie
1

screenshot-to-prd

Extract UI elements and business logic from screenshots into Markdown PRDs.

Community
Intermediate