prd-writer

Transform a user story into a complete PRD with feature breakdown and test plans.

1|3|Updated Feb 28, 2026

Search Tags:#planning #tdd #requirements #risk-management #prd #product-management #design-specification

Ready to run

npx skills add https://github.com/vobbilis/aigile --skill prd-writer-vobbilis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/vobbilis/aigile/tree/main/.github/skills/prd-writer
Command: npx skills add https://github.com/vobbilis/aigile --skill prd-writer-vobbilis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a complete, executable PRD from a user story, enforcing early success criteria and a structured planning workflow to align product and engineering teams.

Core Features & Use Cases

Prompt for the user story (persona, need, outcome) to extract core goals.
Prompt for success criteria BEFORE architecture/design/tasks.
Produce a complete PRD with a feature breakdown, tech stack assumptions, architecture specification, design spec, implementation task breakdown, and a test-driven development plan.
Run the “Ralph Wiggum loop” (gap/risk check) and revise at least once.
Deliver a PRD with explicit sections, measurable acceptance criteria, and a clear implementation plan.

Quick Start

Provide a user story and any constraints, and the skill will prompt for missing inputs and generate a complete, executable PRD.

Frequently Asked Questions about prd-writer

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

FAQPage Schema

How do I turn a user story into a complete PRD with architecture specs and test plans?▼

Generating a PRD from a user story requires prompting for the persona, need, and outcome to extract core goals, then enforcing success criteria before producing feature breakdowns, architecture specs, and test plans.

What is the best way to align product and engineering teams on executable documentation?▼

Executable documentation aligns product and engineering teams by enforcing early success criteria and structured planning workflows, delivering a ready-to-implement PRD with explicit sections, measurable acceptance criteria, and a clear implementation plan.

How do I write a PRD with measurable acceptance criteria and a test-driven development plan?▼

Writing a PRD with measurable acceptance criteria requires defining success criteria before architecture design, then producing an implementation task breakdown and a test-driven development plan to ensure structured, executable documentation.

Does generating a product requirements document require predefined success criteria before architecture design?▼

Generating a product requirements document requires predefined success criteria before architecture design to ensure early alignment, enforce structured planning, and deliver executable documentation with measurable acceptance criteria and risk checks.

What is a gap and risk check loop in product management planning?▼

A gap and risk check loop in product management planning is a revision process that validates the PRD for missing details and potential risks, ensuring the final document enforces explicit success criteria and delivers a ready-to-implement plan.

Can I create a design specification from a user story without providing technical constraints?▼

Creating a design specification from a user story without technical constraints triggers input prompts for missing details, ensuring the resulting PRD includes tech stack assumptions, architecture specifications, and measurable acceptance criteria.