ralph-tui-prd

1. Receive a feature description from the user
2. Ask 3-5 essential clarifying questions (with lettered options) - one set at a time
3. Always ask about quality gates (what commands must pass)
4. After each answer, ask follow-up questions if needed (adaptive exploration)
5. Generate a structured PRD when you have enough context
6. Output the PRD wrapped in [PRD]...[/PRD] markers for TUI parsing

Important: Do NOT start implementing. Just create the PRD.

---

Ask questions one set at a time. Each answer should inform your next questions. Focus on:

• Problem/Goal: What problem does this solve?
• Core Functionality: What are the key actions?
• Scope/Boundaries: What should it NOT do?
• Success Criteria: How do we know it's done?
• Integration: How does it fit with existing features?
• Quality Gates: What commands must pass for each story? (REQUIRED)

Format Questions Like This:

```

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]

1. 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.

Quality Gates Question (REQUIRED)

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

```

Adaptive Questioning

After each response, decide whether to:

• Ask follow-up questions (if answers reveal complexity)
• Ask about a new aspect (if current area is clear)
• Generate the PRD (if you have enough context)

Typically 2-4 rounds of questions are needed.

---

Generate the PRD with these sections:

1. Introduction/Overview

Brief description of the feature and the problem it solves.

2. Goals

Specific, measurable objectives (bullet list).

3. Quality Gates

CRITICAL: List the commands that must pass for every user story.

```markdown

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.

4. User Stories

Each story needs:

• Title: Short descriptive name
• Description: "As a [user], I want [feature] so that [benefit]"
• Acceptance Criteria: Verifiable checklist of what "done" means

Each story should be small enough to implement in one focused AI agent session.

Format:

```markdown

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:

• Acceptance criteria must be verifiable, not vague
• "Works correctly" is bad
• "Button shows confirmation dialog before deleting" is good
• Each story should be independently completable

5. Functional Requirements

Numbered list of specific functionalities:

• "FR-1: The system must allow users to..."
• "FR-2: When a user clicks X, the system must..."

Be explicit and unambiguous.

6. Non-Goals (Out of Scope)

What this feature will NOT include. Critical for managing scope.

7. Technical Considerations (Optional)

• Known constraints or dependencies
• Integration points with existing systems
• Performance requirements

8. Success Metrics

How will success be measured?

9. Open Questions

Remaining questions or areas needing clarification.

---

The PRD will be executed by AI coding agents via ralph-tui. Therefore:

• Be explicit and unambiguous
• User stories should be small (completable in one session)
• Acceptance criteria must be machine-verifiable where possible
• Include specific file paths if you know them
• Reference existing code patterns in the project

---

CRITICAL: Wrap the final PRD in markers for TUI parsing:

```

[PRD]

# PRD: Feature Name

...

...

...

[/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:

1. What is the primary goal?

A. Reduce eye strain for long sessions

B. Match system theme preference

C. Provide visual customization

D. Other

1. 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:

1. Which components need dark mode support?

A. All TUI components

B. Only the main execution view

C. Main view + settings

D. Other

1. 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]

1. 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]

# PRD: Dark Mode for Ralph TUI

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.

• Provide a comfortable viewing experience in low-light environments
• Persist theme preference across sessions
• Apply consistent styling to all TUI components

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

US-001: Add theme configuration

Description: As a user, I want to set my preferred theme (light/dark) so that it persists across sessions.

Acceptance Criteria:

• [ ] Add theme field to .ralph-tui.yaml schema
• [ ] Support values: "light", "dark", "system"
• [ ] Default to "light" for backwards compatibility

US-002: Create dark theme color palette

Description: As a user, I want a soft-contrast dark theme that's easy on the eyes.

Acceptance Criteria:

• [ ] Define dark palette with gray tones (not pure black)
• [ ] Ensure sufficient contrast ratios (WCAG AA)
• [ ] Colors work well for all UI states (selected, hover, disabled)

US-003: Apply theme to TUI components

Description: As a user, I want all TUI components to respect my theme preference.

Acceptance Criteria:

• [ ] Header component uses theme colors
• [ ] Task list uses theme colors
• [ ] Detail panels use theme colors
• [ ] Progress bar uses theme colors
• [ ] Dialogs use theme colors

US-004: Add theme toggle in settings

Description: As a user, I want to toggle themes from within the TUI settings.

Acceptance Criteria:

• [ ] Theme option visible in settings view
• [ ] Changes apply immediately without restart
• [ ] Changes persist to config file

• FR-1: Theme setting must be readable from .ralph-tui.yaml
• FR-2: Theme must apply on TUI startup
• FR-3: Theme changes in settings must apply immediately
• FR-4: All text must maintain readability in both themes

• System theme auto-detection (future enhancement)
• Custom color schemes beyond light/dark
• Per-component theme overrides

• Use existing OpenTUI theming capabilities if available
• Consider creating a ThemeContext for React components
• Minimize re-renders when theme changes

• All components render correctly in dark mode
• No accessibility contrast issues
• Theme persists across sessions

• Should we detect system theme preference automatically in v2?

[/PRD]

---

Before outputting the PRD:

• [ ] Asked clarifying questions with lettered options
• [ ] Asked about quality gates (REQUIRED)
• [ ] Asked follow-up questions when needed
• [ ] Quality Gates section included with project-specific commands
• [ ] User stories are small and independently completable
• [ ] User stories do NOT include quality gate commands (they're in the Quality Gates section)
• [ ] Functional requirements are numbered and unambiguous
• [ ] Non-goals section defines clear boundaries
• [ ] PRD is wrapped in [PRD]...[/PRD] markers