prd

Interviews users section by section to write a Product Requirements Document to docs/01_product/01_prd.md.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill prd-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/prd
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill prd-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a PRD from scratch often produces vague problem statements, undefined target users, and unmeasurable success criteria. This Skill acts as a Product Coach that interviews you section by section, pushes back on vague answers in real time, and produces a strategically sound PRD file. ## Core Features & Use Cases - Guided Interview: Walks through seven sections (problem, vision, identity, target user, value proposition, scope, success indicators) using structured questions with pre-filled context from existing docs. - Coaching Pushback: Challenges generic answers like "users are happy" or "everyone can use it" and demands measurable indicators, explicit non-users, and at least two out-of-scope exclusions. - Slice Signal Extraction: Silently captures plain-language system requirements during the interview for later use by the slices-discovery skill. - Use Case: You have a rough idea for a shared-expense app. Run this Skill to turn scattered thoughts into a complete PRD at docs/01_product/01_prd.md with a confirmed executive summary before anything is written. ## Quick Start Ask the assistant to create a PRD for your product idea and answer the section-by-section interview questions.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a PRD for a new software product?▼

Run this Skill and answer its section-by-section interview covering problem, vision, target user, value proposition, scope, and success indicators. It pre-fills answers from existing docs, confirms an executive summary with you, then writes the PRD to docs/01_product/01_prd.md.

What sections should a product requirements document include?▼

This Skill generates eight sections: Problem, Product Vision, Product Identity, Target User, Value Proposition, Out of Scope, Success Indicators, and Slice Signals. It enforces at least two explicit non-user types and two scope exclusions.

Can I update an existing PRD instead of creating a new one?▼

Yes. Before interviewing, the Skill checks whether docs/01_product/01_prd.md already exists and asks whether you want to update it or start from scratch. It also scans README and other docs to pre-fill known answers.

Why does the PRD interview reject vague success metrics?▼

Indicators like "users are happy" cannot be verified, so the Skill requires each metric to state what is measured, a directional target, and how it is observed. Unmeasurable statements are treated as hopes, not indicators.

What are slice signals in a PRD?▼

Slice signals are plain-language descriptions of what the system must support, extracted silently from your interview answers rather than asked directly. They are stored in a dedicated PRD section and consumed later by the slices-discovery skill.