Agent skill · product strategy · borghei
create-prd
PRD scaffolding expert that generates structured product requirements documents using an 8-section framework, problem framing canvas, and working-backwards press release. Use to spec a new product or feature.
Why this skill is useful
Adds a Python script that automates the generation of structured PRDs using a specific 8-section framework, which the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
PRD Scaffolding Expert Overview Structured product requirements document creation using a proven 8-section framework. This skill produces clear, jargon-free PRDs that communicate what to build, why it matters, and how success is measured. Every PRD generated follows a consistent structure that keeps engineering, design, and business stakeholders aligned. Core Capabilities Pre-PRD framing — Problem Framing Canvas (user-perspective narrative) and Working Backwards Press Release sharpen the problem before solutions. 8-section PRD framework — Summary, Contacts, Background, Objective (SMART KRs), Market Segments (JTBD), Value Proposition (Value Curve), Solution (P0/P1/P2), Release. Plain-language discipline — one idea per sentence, specificity over abstraction, 10-second executive test. Scaffolder automation — prdscaffolder.py generates the skeleton with guided placeholders. When to Use New Product Initiative -- Starting a product from scratch and need a comprehensive spec before development begins. Feature Expansion -- Adding significant functionality to an existing product that requires cross-team alignment. Stakeholder Alignment -- Need a single document that answers "what are we building and why?" for everyone involved. Clarify First Before generating the PRD, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Core problem — one sentence in the user's words; who hurts and how (drives Background + Objective) [ ] Target reader — exec, engineering, or mixed (sets altitude and which of the 8 sections matter most) [ ] Success metric — the SMART KR that defines "it worked" (drives Objective) [ ] Scope boundary — what is explicitly NOT in this release (drives Solution P0/P1/P2 + Release) Stop rule: ask only the 2–3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the PRD. Quick Start 1. Gather context: product name, target segment, core problem. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/create-prd