prd-writer

Generate structured PRDs with scope, risks, MVP, and acceptance criteria.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/yaochangyu/ai-dev-toolkit --skill prd-writer-yaochangyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/yaochangyu/ai-dev-toolkit/tree/main/.github/skills/prd-writer
Command: npx skills add https://github.com/yaochangyu/ai-dev-toolkit --skill prd-writer-yaochangyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams craft complete, structured, and executable PRDs that align engineering feasibility, risk management, scope clarity, and unambiguous acceptance criteria.

Core Features & Use Cases

  • PRD scaffolding: Generates a full PRD structure including Basic Information, TL;DR, Goals, Problems, Scope, Non-goals, Risks, MVP, Delivery Plan, Acceptance Criteria, and Appendix.
  • Risk & Compliance guidance: Identifies potential risks, regulatory considerations, privacy and data handling notes, and mitigation strategies.
  • Deliverable & Verification: Produces deliverables with testable acceptance criteria and verification strategies for QA.

Quick Start

Provide a brief product concept, target users, and success metrics; I will generate a complete PRD outline with sections for scope, risks, MVP, and acceptance criteria.

Frequently Asked Questions about prd-writer

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

FAQPage Schema
How do I draft a complete PRD that includes risk management and MVP scope?

Drafting a complete PRD requires structuring scope, goals, timelines, user personas, risks, MVP, delivery plans, and acceptance criteria. This ensures testable requirements and clear engineering handoffs across product initiatives.

What sections should be included in a product requirements document for engineering handoff?

A PRD for engineering handoff should include Basic Information, TL;DR, Goals, Problems, Scope, Non-goals, Risks, MVP, Delivery Plan, Acceptance Criteria, and Appendix to ensure testable requirements and clear handoffs.

How do I write testable acceptance criteria for a product requirements document?

Writing testable acceptance criteria involves defining deliverables with specific verification strategies for QA. This ensures the PRD guides engineering feasibility and produces unambiguous requirements that can be validated.

Can I generate a PRD outline from just a brief product concept and target users?

Generating a PRD outline from a brief concept is possible by providing target users and success metrics. The framework scaffolds the full structure, generating sections for scope, risks, MVP, and acceptance criteria.

How do I identify regulatory compliance and data privacy risks when defining product scope?

Identifying regulatory compliance and data privacy risks involves generating specific risk and compliance guidance sections within the PRD. This includes privacy data handling notes and mitigation strategies across product initiatives.

What is the best way to structure an MVP delivery plan in a PRD?

Structuring an MVP delivery plan in a PRD requires defining clear scope, non-goals, and delivery timelines. This aligns engineering feasibility with risk management to produce actionable, executable product requirements.