write-prd

Name: write-prd
Availability: InStock
Author: Sir-chawakorn

Generate structured Product Requirements Documents with acceptance criteria and scope boundaries.

9|3|Updated Jun 13, 2026

Search Tags:#planning #scoping #specification #requirements #prd #product-management

Ready to run

npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-prd-sir-chawakorn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-prd
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/write-prd
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-prd-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of poorly defined product requirements by enforcing a structured, evidence-first approach that prevents scope creep and ensures engineering alignment.

Core Features & Use Cases

Interactive Discovery: Guides the user through five critical gaps (Problem, User, Metric, Constraints, Scope) before drafting.
Structured PRD Generation: Produces a comprehensive document including goals, counter-metrics, P0-P2 requirements, and acceptance criteria.
Use Case: Use this when you have a vague feature idea and need to transform it into a rigorous, testable specification that engineering can immediately begin planning.

Quick Start

Ask the AI to write a PRD for your new feature and answer the discovery questions it provides to generate the final document.

Frequently Asked Questions about write-prd

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

FAQPage Schema

How do I write a product requirements document that prevents scope creep?▼

To write a product requirements document that prevents scope creep, use an evidence-first approach that defines explicit scope boundaries, measurable success metrics, and counter-metrics. This ensures engineering alignment and rigorous feature prioritization.

What is the best way to structure a PRD for engineering planning?▼

The best way to structure a PRD for engineering planning is to include clear problem statements, measurable success metrics, P0-P2 prioritized feature requirements, and testable acceptance criteria to guide implementation.

How do I turn a vague feature idea into a testable product specification?▼

To turn a vague feature idea into a testable product specification, complete an interactive discovery process covering five critical gaps: Problem, User, Metric, Constraints, and Scope before drafting the final requirements document.

Can I generate implementation-ready product requirements without prior documentation?▼

Yes, you can generate implementation-ready product requirements without prior documentation. The interactive discovery process guides you through defining the problem, metrics, and constraints to produce the final specification from scratch.

What should be included in product management scoping to ensure feature testability?▼

Product management scoping should include clear problem definitions, user constraints, measurable metrics, and explicit scope boundaries. Adding P0-P2 prioritized requirements and testable acceptance criteria ensures feature testability.