skills.rest
DanialDaeHyunNam
DanialDaeHyunNamCOMMUNITY
Explore all skills by this author →
GitHub

prd-collab

Guide teams through a 12-step workflow to create structured PRDs.

6|Updated Mar 15, 2026
Search Tags:#workflow#versioning#collaboration#prd#wireframes#product-requirements#team-alignment
One-click install
npx skills add https://github.com/DanialDaeHyunNam/claude-starter --skill prd-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-collab
Source: https://github.com/DanialDaeHyunNam/claude-starter/tree/main/.claude/skills/prd-collab
Command: npx skills add https://github.com/DanialDaeHyunNam/claude-starter --skill prd-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to transform abstract product ideas into concrete, shareable PRDs, leading to misaligned goals and costly rework.

Core Features & Use Cases

  • A 12-step workflow that guides ideation to detailed PRDs, ensuring alignment across disciplines.
  • Structure supports feature hierarchy, goals, emotional journey, and versioned PRD management.
  • Ideal for product discovery, cross-functional collaboration, and formalizing product requirements.

Quick Start

Invoke /prd-collab to start a new PRD exploration and guide the team through the 12-step workflow.

Frequently Asked Questions about prd-collab

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

FAQPage Schema
How do I turn abstract product ideas into structured PRDs for cross-functional team alignment?▼

A structured PRD workflow guides teams from ideation to detailed documentation through 12 disciplined steps, ensuring cross-functional team alignment and reducing costly rework caused by misaligned goals.

What is the best way to manage versioning and collaboration during product discovery?▼

The best way to manage versioning and collaboration is using a structured 12-step workflow that organizes PRD files under docs/prd, tracking feature hierarchy, goals, and emotional journeys for formalized product requirements.

Do I need wireframes to complete the product requirements documentation steps?▼

Yes, pencil wireframes are required to complete the product requirements documentation steps. The 12-step workflow specifically requires pencil wireframes for steps 9 through 11 to finalize the PRD.

Can I resume a PRD collaboration workflow if the session is interrupted?▼

Yes, you can resume a PRD collaboration workflow if interrupted by invoking /prd-collab with a feature-name parameter, allowing you to continue the 12-step process across cross-functional teams without losing progress.

How does a 12-step PRD workflow structure team alignment and product requirements?▼

A 12-step PRD workflow structures team alignment by implementing Step 0 through Step 11, organizing product requirements into feature hierarchy, goals, and emotional journey documentation for cross-functional collaboration.

What are the limitations of using a structured PRD workflow for product discovery?▼

Limitations of a structured PRD workflow include rigid sequential progression through 12 steps and the mandatory creation of pencil wireframes for steps 9-11, which may restrict rapid prototyping during early product discovery.

Related Skills

Explore More Product & Management Skills→
v24kuonv24kuon

brainstorming

Converts abstract product ideas into technical specifications and implementation plans through iterative dialogue.

Community
Intermediate
jayhjenkinsjayhjenkins
1

prd-creation

Guide an interactive eight-phase session to create and validate Product Requirements Documents.

Community
Advanced
elijahmurrayelijahmurray
2

pr-create

Create pull requests and validate documentation before submission.

Community
Basic
abhilash-nandkumarabhilash-nandkumar

user-story-fundamentals

Capture user requirements into structured user stories with acceptance criteria.

Community
Intermediate