Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads issues or prd.json for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
88
84%
Does it follow best practices?
Impact
96%
1.52xAverage score across 3 eval scenarios
Passed
No known issues
PRD structure and quality gates
PRD markers present
0%
100%
No implementation code
100%
100%
Introduction/Overview section
100%
100%
Goals section with measurable bullets
66%
66%
Quality Gates section present
100%
100%
Correct quality commands
100%
100%
Browser verification in quality gates
100%
100%
User stories US-NNN format
0%
100%
As-a user story descriptions
100%
100%
Quality gates not duplicated in stories
12%
100%
Verifiable acceptance criteria
100%
100%
Functional Requirements section
0%
100%
Non-Goals section
100%
100%
Success Metrics section
100%
100%
Open Questions section
100%
100%
Stories independently scoped
50%
75%
clarifying questions and adaptive exploration
Questions shown before PRD
100%
100%
Lettered options in questions
0%
100%
3-5 questions per round
33%
66%
Quality gates question included
50%
100%
Problem/goal question covered
100%
100%
Scope/boundaries question covered
60%
100%
Adaptive follow-up shown
0%
28%
PRD markers present
0%
100%
Quality Gates section present
37%
100%
Non-Goals section present
100%
100%
User stories from question insights
83%
100%
Open Questions section
100%
100%
No code implementation
100%
100%
Functional requirements numbered
100%
100%
Multiple Q&A rounds evident
16%
100%
user story quality and scope discipline
PRD markers present
0%
100%
No implementation code
100%
100%
Quality Gates section present
50%
100%
Correct quality commands used
100%
100%
Quality gates not in story criteria
0%
100%
US-NNN story numbering
0%
100%
As-a story descriptions
100%
100%
Verifiable acceptance criteria
88%
100%
Stories independently scoped
71%
100%
Substantive Non-Goals section
100%
100%
Functional requirements FR-N format
0%
100%
Goals section measurable
60%
100%
Success Metrics section
100%
100%
Open Questions section
100%
100%
Explicit scope rationale
100%
100%
1d4670f
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.