skills.rest
viethahong
viethahongCOMMUNITY
Explore all skills by this author →
GitHub

prd-writing

Generate PRDs with goals, user flows, requirements, acceptance criteria, and edge cases.

2|Updated Apr 25, 2026
Search Tags:#edge cases#acceptance criteria#agile#user stories#prd#product requirements
One-click install
npx skills add https://github.com/viethahong/business-skills --skill prd-writing-viethahong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-writing
Source: https://github.com/viethahong/business-skills/tree/main/skills/product/prd-writing
Command: npx skills add https://github.com/viethahong/business-skills --skill prd-writing-viethahong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translating business ideas and vague requirements into a clear, actionable Product Requirements Document (PRD) that aligns product, design, and engineering teams.

Core Features & Use Cases

  • Generate a complete PRD with Goals, User Flows, Functional & Non-functional Requirements, Acceptance Criteria, and Edge Cases.
  • Create feature specifications from User Stories and technical constraints, ensuring testable criteria.
  • Provide structured outputs ready for review, QA, and handoff to engineering teams across Agile projects.

Quick Start

Provide a complete PRD for a feature based on business goals, including goals, user flows, requirements, acceptance criteria, and edge cases.

Frequently Asked Questions about prd-writing

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

FAQPage Schema
How do I write a PRD that includes user flows and acceptance criteria?▼

To write a PRD with user flows and acceptance criteria, translate business goals and user stories into structured sections covering functional requirements, edge cases, and testable criteria for engineering handoff.

What is the best way to translate user stories into feature specifications for Agile projects?▼

The best way to translate user stories into feature specifications is to map technical constraints and business goals against structured outputs, generating testable acceptance criteria and documented edge cases ready for QA review.

Can I generate non-functional requirements alongside functional requirements in a PRD?▼

Yes, you can generate non-functional requirements alongside functional requirements in a PRD. Structured PRD generation explicitly includes both categories to ensure engineering teams receive comprehensive system and behavioral constraints.

How do you document edge cases in product requirements documents?▼

Documenting edge cases in product requirements involves analyzing user flows and technical constraints to identify boundary conditions, then explicitly listing these scenarios alongside acceptance criteria to ensure robust engineering implementation.

Does PRD generation work for aligning design and engineering teams around vague requirements?▼

PRD generation works for aligning design and engineering teams by taking vague business ideas and converting them into clear, actionable product requirements documents with defined goals, user flows, and structured technical specifications.

Related Skills

Explore More Product & Management Skills→
labs21-devlabs21-dev
28

feature-spec

Draft PRD-style feature specifications with goals, metrics, and open questions.

Official
Advanced
ramybarsoumramybarsoum

create-tickets

Convert approved Feature Doc Section 5 use cases into engineering tickets for Linear, Jira, or text.

Community
Intermediate
AlfxjxAlfxjx

my-design

Provide UI/UX design guidance for wireframing, prototyping, and visual design.

Community
Intermediate
AlekseiULAlekseiUL
64

business-architect

Transform raw ideas into structured business plans with milestones and lean canvas outputs.

Community
Advanced