skills.rest
ucasYToo
ucasYTooCOMMUNITY
Explore all skills by this author →
GitHub

requirement-workflow

Guide requirement clarification and PRD generation through /req, /plan, and /tdd workflows.

Updated Apr 5, 2026
Search Tags:#workflow#planning#templates#discovery#prd#stakeholders#requirement
One-click install
npx skills add https://github.com/ucasYToo/claude-code-configs --skill requirement-workflow-ucasytoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirement-workflow
Source: https://github.com/ucasYToo/claude-code-configs/tree/main/skills/requirement-workflow
Command: npx skills add https://github.com/ucasYToo/claude-code-configs --skill requirement-workflow-ucasytoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable framework to guide requirement discovery, analysis, and PRD generation, automatically loading during /req commands or requirements analysis.

Core Features & Use Cases

  • Structured clarifying prompts to elicit stakeholders, goals, constraints, risks, and scope.
  • Research and validation practices to assess user scenarios, market context, and business impact.
  • PRD generation templates and workflow guidance that align plans with development milestones.

Quick Start

Initiate the workflow by running /req to clarify requirements, then proceed with /plan to draft the implementation plan and finally start /tdd to begin development.

Frequently Asked Questions about requirement-workflow

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

FAQPage Schema
How do I generate a PRD from initial product requirements?▼

To generate a PRD, use the /req command to clarify stakeholders, goals, and scope through structured prompts and 5W analysis. This workflow guides requirement discovery and produces a standardized Product Requirements Document.

What is the best way to align stakeholders before starting software design?▼

The best way to align stakeholders is running structured requirement clarification workflows like /req to elicit constraints, risks, and business impact. This ensures early discovery aligns plans with development milestones before design begins.

How does 5W analysis work for product requirement discovery?▼

5W analysis for requirement discovery works by applying structured clarifying prompts to elicit stakeholders, goals, constraints, and scope. This framework systematically validates user scenarios and business impact to document precise requirements.

Can I use this workflow to draft an implementation plan after PRD generation?▼

Yes, you can draft an implementation plan after PRD generation by running the /plan command. This maps the clarified requirements into actionable development milestones before proceeding with /tdd to begin coding.

When do I need a reusable PRD template for requirement documentation?▼

You need a reusable PRD template when standardizing requirement outcomes across multiple projects. It ensures consistent documentation of goals, risks, and scope during early discovery, preventing misalignment between design and development teams.

Related Skills

Explore More Product & Management Skills→
hb9397hb9397

design-doc

Generate structured design documents and PRDs from raw project inputs.

Community
Advanced
nseluganseluga

implement

Implement tasks from PRDs or issues with TDD and typechecking.

Community
Intermediate
ValueMediaValueMedia

10x-roadmap

Generate a development roadmap from a Product Requirements Document.

Official
Advanced
serejarisserejaris
215

pm-brainstorm

Structure product brainstorming sessions with SCAMPER, 5 Whys, and Impact/Effort screening.

Community
Advanced