skills.rest
pipixia-labs
pipixia-labsOFFICIAL
Explore all skills by this author →
GitHub

pm-spec

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

38|3|Updated Apr 8, 2026
Search Tags:#spec#prd#product-management#user-stories#brief#rollout-plan#design-notes
One-click install
npx skills add https://github.com/pipixia-labs/creative-claw --skill pm-spec-pipixia-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/pipixia-labs/creative-claw/tree/main/skills/design-knowledge-and-skills/skills/pm-spec
Command: npx skills add https://github.com/pipixia-labs/creative-claw --skill pm-spec-pipixia-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to convert a vague brief into a concise, shareable PRD. This Skill converts a design brief into a complete one-page product spec, ensuring alignment and a consistent structure.

Core Features & Use Cases

  • Produce a complete one-page PRD that includes header, summary, Problem, Goals & non-goals, Success metrics, User stories, Scope milestones, and Open questions.
  • Support design notes, rollout plan, and open questions for cross-functional planning.
  • Use cases include converting a design brief, a feature brief, or a PRD request into an executable spec document for desktop product teams.

Quick Start

Provide a brief for a feature, and the skill will generate a complete one-page PRD ready for review.

Frequently Asked Questions about pm-spec

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

FAQPage Schema
How do I convert a design brief into a product spec?▼

You can convert a design brief into a product spec by inputting the brief and generating a structured one-page PRD. The output includes sections for problem, goals, success metrics, user stories, scope milestones, and open questions.

What sections should a one-page PRD include for product teams?▼

A one-page PRD for product teams should include sections for the problem, goals and non-goals, success metrics, user stories, scope milestones, and open questions. It also supports design notes and rollout planning.

Can I generate user stories and rollout plans from a feature brief?▼

Yes, you can generate user stories and rollout plans directly from a feature brief. The system produces a structured HTML artifact containing scope milestones, design notes, and rollout plans for desktop product teams.

Does this approach work for desktop product experiences only?▼

This PRD generation approach applies specifically to desktop product experiences. It structures briefs, scope, user stories, and rollout plans to ensure alignment and consistent documentation for product teams in that context.

How do I structure open questions and design notes in a PRD?▼

You structure open questions and design notes in a PRD by using dedicated sections within the one-page spec. This supports cross-functional planning by capturing design context and unresolved issues alongside scope milestones.

Related Skills

Explore More Product & Management Skills→
az9713az9713

pm-spec

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

Community
Advanced
clearclownclearclown
3

cc-sdd

Generate design.md and task plans from requirements using spec-driven development.

Community
Advanced
coco-decoco-de

Scrum Master

Break epics into user stories and sync sprint artifacts with ZenHub.

Official
Advanced
kevinlinkevinlin
14

feature-spec

Generate a structured PRD with problem statements, goals, user stories, and acceptance criteria.

Community
Advanced