prd

Generate a planning-ready Product Requirements Document with goals, metrics, and acceptance criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents confusing, assumption-driven AI coding sessions by translating a product idea into a clear, testable contract for what success means and what is explicitly out of scope.

Core Features & Use Cases

  • PRD that produces planning-ready contracts: Frames problem, users, goals, non-goals, risks, and measurable success metrics so downstream planning doesn’t guess.
  • Goal Source Candidates → Goal Source Contract: Preserves lineage from user-stated outcomes into stable G0... goal objects with explicit verifiers and done thresholds.
  • Evidence-first guardrails: Requires reading existing PRD/spec artifacts and records approvals, evidence paths, and blockers instead of inventing requirements.

Quick Start

Use this skill to draft a PRD by asking your AI to produce a planning-ready Product Requirements Document for your specific user-facing feature.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a product requirements document with measurable success metrics?▼

A product requirements document with measurable success metrics translates product requests into planning-ready contracts by defining problem, users, non-goals, and explicit instrumentation boundaries. This frames feature scope and establishes verifiable success metrics for downstream planning.

How do I define acceptance criteria and goal lineage for an MVP scope?▼

Defining acceptance criteria and goal lineage for an MVP scope requires preserving outcome lineage from user-stated goals into stable goal objects using a Goal Source Contract. This contract specifies explicit verifiers and done thresholds to ensure the MVP scope is testable and measurable.

What is a Goal Source Contract and how does it prevent assumption-driven feature development?▼

A Goal Source Contract prevents assumption-driven feature development by mapping user-stated outcomes into stable goal objects with explicit verifiers and done thresholds. It records evidence paths and approvals, ensuring downstream planning does not guess at success criteria.

How do I create a risk register and instrumentation boundaries for a replacement feature PRD?▼

Creating a risk register and instrumentation boundaries for a replacement feature PRD involves reading prior spec artifacts and explicitly defining what is out of scope. This evidence-first approach records blockers and missing approvals to prevent inventing requirements during implementation.

When should I stop drafting product requirements due to missing evidence or approvals?▼

You should stop drafting product requirements due to missing evidence or approvals when required prior spec artifacts are absent. The evidence-first guardrails mandate stopping with blockers if necessary evidence, approvals, or scope definitions are missing.