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.
| name | ralph-tui-prd |
| description | 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. |
Create detailed Product Requirements Documents optimized for AI agent execution via ralph-tui.
[PRD]...[/PRD] markers for TUI parsingImportant: Do NOT start implementing. Just create the PRD.
Ask questions one set at a time. Each answer should inform your next questions. Focus on:
1. What is the primary goal of this feature?
A. Improve user onboarding experience
B. Increase user retention
C. Reduce support burden
D. Other: [please specify]
2. Who is the target user?
A. New users only
B. Existing users only
C. All users
D. Admin users only
This lets users respond with "1A, 2C" for quick iteration.
Always ask about quality gates - these are project-specific:
What quality commands must pass for each user story?
A. pnpm typecheck && pnpm lint
B. npm run typecheck && npm run lint
C. bun run typecheck && bun run lint
D. Other: [specify your commands]
For UI stories, should we include browser verification?
A. Yes, use dev-browser skill to verify visually
B. No, automated tests are sufficient
After each response, decide whether to:
Typically 2-4 rounds of questions are needed.
Generate the PRD with these sections:
Brief description of the feature and the problem it solves.
Specific, measurable objectives (bullet list).
CRITICAL: List the commands that must pass for every user story.
## Quality Gates
These commands must pass for every user story:
- `pnpm typecheck` - Type checking
- `pnpm lint` - Linting
For UI stories, also include:
- Verify in browser using dev-browser skill
This section is extracted by conversion tools (ralph-tui-create-json, ralph-tui-create-beads) and appended to each story's acceptance criteria.
Each story needs:
Each story should be small enough to implement in one focused AI agent session.
Format:
### US-001: [Title]
**Description:** As a [user], I want [feature] so that [benefit].
**Acceptance Criteria:**
- [ ] Specific verifiable criterion
- [ ] Another criterion
Note: Do NOT include quality gate commands in individual story criteria - they are defined once in the Quality Gates section and applied automatically during conversion.
Important:
Numbered list of specific functionalities:
Be explicit and unambiguous.
What this feature will NOT include. Critical for managing scope.
How will success be measured?
Remaining questions or areas needing clarification.
The PRD will be executed by AI coding agents via ralph-tui. Therefore:
CRITICAL: Wrap the final PRD in markers for TUI parsing:
[PRD]
# PRD: Feature Name
## Overview
...
## Quality Gates
...
## User Stories
...
[/PRD]
File naming: The TUI will save to ./tasks/prd-[feature-name].md
User: Create a PRD for adding dark mode to the TUI
Assistant: I'll help you create a PRD for dark mode. Let me ask a few questions:
What is the primary goal? A. Reduce eye strain for long sessions B. Match system theme preference C. Provide visual customization D. Other
Should the setting persist? A. Yes, save to config file B. No, session only C. Follow system preference
User: 1A, 2A
Assistant: Great! A couple more questions:
Which components need dark mode support? A. All TUI components B. Only the main execution view C. Main view + settings D. Other
What quality commands must pass for each story? A. pnpm typecheck && pnpm lint B. npm run typecheck && npm run lint C. bun run typecheck D. Other: [specify]
For UI stories, include browser verification? A. Yes, use dev-browser skill B. No, automated tests sufficient
User: 3A, 4A, 5A
Assistant: Perfect, I have enough to generate the PRD.
[PRD]
Add dark mode support to ralph-tui to reduce eye strain during long orchestration sessions. The feature will apply to all TUI components and persist the user's preference in the config file.
These commands must pass for every user story:
pnpm typecheck - Type checkingpnpm lint - LintingFor UI stories, also include:
Description: As a user, I want to set my preferred theme (light/dark) so that it persists across sessions.
Acceptance Criteria:
theme field to .ralph-tui.yaml schemaDescription: As a user, I want a soft-contrast dark theme that's easy on the eyes.
Acceptance Criteria:
Description: As a user, I want all TUI components to respect my theme preference.
Acceptance Criteria:
Description: As a user, I want to toggle themes from within the TUI settings.
Acceptance Criteria:
.ralph-tui.yamlBefore outputting the PRD:
[PRD]...[/PRD] markersConvert PRDs to prd.json format for ralph-tui execution. Creates JSON task files with user stories, acceptance criteria, and dependencies. Triggers on: create prd.json, convert to json, ralph json, create json tasks.
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI). Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads-rust as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads, br beads.
Convert PRDs to beads for ralph-tui execution. Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads.
