ralph-tui-create-beads

Convert PRDs into epic and child beads with dependencies and quality gates.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/strataga/claude-skill-inception --skill ralph-tui-create-beads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-tui-create-beads
Source: https://github.com/strataga/claude-skill-inception/tree/main/ralph-tui-create-beads
Command: npx skills add https://github.com/strataga/claude-skill-inception --skill ralph-tui-create-beads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates converting a PRD into actionable beads for ralph-tui, producing an epic bead with child beads for each user story and wiring dependencies and quality gates for deterministic execution.

Core Features & Use Cases

  • PRD to Epic Conversion: Creates a master epic bead that represents the feature set described by the PRD.
  • Child Beads per User Story: Generates individual beads for each user story found in the PRD, including acceptance criteria and PRD-specific quality gates.
  • Dependency Wiring: Automatically sets dependencies in the correct order (e.g., schema → backend → UI) to ensure coherent execution flow.
  • Output Ready for Ralph-tui: Produces data in .beads/beads.jsonl ready to run with the ralph-tui tracker.

Quick Start

Provide a PRD markdown file to the skill. It will generate an epic bead and child beads and write them to .beads/beads.jsonl. Then run: ralph-tui run --tracker beads --epic <EPIC_ID>

Frequently Asked Questions about ralph-tui-create-beads

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

FAQPage Schema
How do I convert a PRD into executable tasks for autonomous execution?

To convert a PRD into executable tasks, this Skill parses user stories and quality gates to generate an epic bead with child beads, outputting ready-to-run data in the .beads/beads.jsonl file.

How does dependency wiring work when generating user stories from a PRD?

Dependency wiring automatically sets execution order for child beads, such as schema before backend before UI, ensuring coherent execution flow across all generated user stories from the PRD.

Can I use this to automate PRD to epic conversion for my product team workflow?

Yes, this automates PRD to epic conversion for product team workflows by creating a master epic bead representing the feature set, alongside individual child beads for each user story found in the PRD.

What's the best way to run beads after generating them from a PRD markdown file?

After generating beads from a PRD markdown file, run them using the ralph-tui tracker by executing the command: ralph-tui run --tracker beads --epic <EPIC_ID>.

Does this workflow generate quality gates and acceptance criteria for each user story bead?

Yes, the workflow generates individual child beads for each user story found in the PRD, explicitly including acceptance criteria and PRD-specific quality gates for deterministic execution.

Why do I need to provide a PRD markdown file to generate beads?

You need to provide a PRD markdown file because the parser relies on extracting user stories and quality gates from that specific format to wire dependencies and produce the .beads/beads.jsonl output.