prd-writer

Generate structured PRDs with problem statements, acceptance criteria, success metrics, and scope.

6|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/vibbs/company-os --skill prd-writer-vibbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/vibbs/company-os/tree/main/.claude/skills/prd-writer
Command: npx skills add https://github.com/vibbs/company-os --skill prd-writer-vibbs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs), ensuring all necessary components like problem statements, success metrics, and scope are clearly defined, preventing scope creep and misaligned development efforts.

Core Features & Use Cases

  • Structured PRD Generation: Creates PRDs with all essential sections: problem statement, success metrics, acceptance criteria, scope boundaries, dependencies, risks, and measurement plans.
  • Discovery Validation Integration: Incorporates findings for novel features, assessing risks and validating assumptions.
  • Use Case: When a new feature is proposed, use this Skill to generate a detailed PRD that Engineering can use to create an RFC, ensuring all requirements are captured upfront.

Quick Start

Use the prd-writer skill to generate a PRD for a new user authentication feature.

Frequently Asked Questions about prd-writer

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

FAQPage Schema
How do I generate a product requirements document with clear scope boundaries?

To generate a product requirements document, input your feature proposal to produce a structured PRD containing problem statements, acceptance criteria, success metrics, and scope boundaries to prevent scope creep.

What is the best way to define success metrics and map them to analytics events?

Defining success metrics and mapping them to analytics events is handled during PRD generation, aligning product goals with measurable tracking plans and ensuring development efforts match intended outcomes.

How do I validate assumptions for novel features before writing a PRD?

Validating assumptions for novel features uses discovery validation integration, assessing risks and validating findings before finalizing the product requirements document to ensure engineering alignment.

Can I use this to create an artifact for engineering to build an RFC?

Yes, you can use this to create a detailed PRD that engineering teams use to create an RFC, ensuring all problem statements, dependencies, and requirements are captured upfront.

What sections are included in a structured product requirements document?

A structured product requirements document includes problem statements, success metrics, acceptance criteria, scope boundaries, dependencies, risks, and measurement plans for comprehensive feature definition.

When do I need formal scope management for feature definition?

Formal scope management for feature definition is needed when proposing new features, utilizing a PRD to establish clear boundaries and prevent misaligned development efforts across product and engineering teams.