prd

Create evidence-backed living PRDs with phased execution artifacts for software planning.

209|27|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/golbin/agent-skills --skill prd-golbin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/golbin/agent-skills/tree/main/skills/prd
Command: npx skills add https://github.com/golbin/agent-skills --skill prd-golbin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams avoid vague or outdated specs by producing a compact, executable Product Requirements Document (PRD) that is continuously updated as implementation uncovers new information.

Core Features & Use Cases

  • Evidence-backed living PRDs: creates or updates PRDs grounded in reviewed project context (code, tests, docs, configs, APIs, and relevant references).
  • Phase-based execution plans: structures work into ordered phases with checklists, discovery gates, validation strategies, and phase-end reviews.
  • Split-file context when plans grow: automatically chooses single-file or split-file mode and links context/phase files under tasks/ to keep the master PRD readable.

Quick Start

Ask an AI agent to run the prd skill to create an evidence-backed PRD and phase execution plan for the feature you want to implement, writing the resulting files under tasks/.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create an evidence-backed product requirements document for a new software feature?

An evidence-backed product requirements document is generated by discovering existing system behavior through code, tests, and APIs, then translating intent into functional requirements with defined validation gates.

What is phase-based execution planning in a living PRD?

Phase-based execution planning structures work into ordered phases with checklists, discovery gates, validation strategies, and phase-end reviews to keep requirements continuously updated as implementation progresses.

How do I keep a large product requirements document readable as the execution plan grows?

You can maintain readability by using split-file context mode, which automatically links context and phase files under the tasks/ directory instead of bloating the master PRD.

Can I update a PRD without losing prior checkbox progress and edits?

Yes, updating a living PRD preserves prior checkboxes and edits, ensuring continuous tracking of implementation progress while incorporating newly discovered project context.

When should I use a risk-appropriate validation strategy for product requirements?

A risk-appropriate validation strategy should be applied during phase discovery gates to ensure functional and non-functional requirements meet the correct review criteria before proceeding.

Does this PRD generation method require specific input formats for project context?

It requires YAML frontmatter-driven identification and strict use of tasks/ markdown outputs, reviewing existing code, tests, docs, configs, and APIs to ground the requirements.