ralph-tui-create-beads-rust_skill

This skill converts PRDs to beads for ralph-tui using beads-rust, creating an epic and child stories with quality gates and dependencies.
  • TypeScript

1.5k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill subsy/ralph-tui --skill ralph-tui-create-beads-rust

  • SKILL.md10.8 KB

Overview

This skill converts a PRD into beads for ralph-tui autonomous execution using beads-rust (br CLI). It creates an epic linking back to the PRD and a child bead for each user story, appending quality gates and wiring dependencies. Use it when you have a markdown or text PRD and want runnable beads ready for ralph-tui. It outputs br create and br dep add commands with safe HEREDOC descriptions.

How this skill works

The skill extracts the PRD's Quality Gates section and classifies universal and UI-specific gates. It generates an epic bead with the feature description and one bead per user story, embedding acceptance criteria plus the extracted quality gates. It orders stories by dependency (schema → backend → UI), sets priorities, and emits br dep add commands to link beads. All descriptions use <<'EOF' HEREDOC to preserve special characters for safe shell execution.

When to use it

  • You have a PRD in markdown or plain text and want ralph-tui to execute the work via beads-rust.
  • You need an epic and well-ordered, right-sized user stories with verifiable acceptance criteria.
  • You want quality gates (typecheck/lint/browser checks) enforced for every story.
  • You need ready-to-run br create and br dep add commands to populate .beads/ for ralph-tui.

Best practices

  • Always extract Quality Gates first; ask the user for gates if the PRD lacks them.
  • Keep each story small enough to complete in one ralph-tui iteration (describe in 2–3 sentences).
  • Order stories by dependencies: schema → backend → UI; add dep links after creating beads.
  • Append universal and UI-specific quality gates to each bead's acceptance criteria.
  • Use <<'EOF' (single-quoted) for HEREDOC to avoid shell interpolation of backticks or $variables.
  • Run br sync --flush-only after creation to export .beads/issues.jsonl for tracking

Example use cases

  • Convert a Friends Outreach PRD into an epic and three child beads (schema, UI toggle, filter) with dependencies and quality gates.
  • Split a large feature into multiple right-sized beads for iterative ralph-tui runs.
  • Add browser verification to UI stories automatically when the PRD specifies it.
  • Prepare beads for CI quality checks by appending pnpm/npm commands to each story's acceptance criteria.

FAQ

Ask the user for required commands or default to a sensible gate like npm run typecheck; include that in every bead's acceptance criteria.

How are dependencies represented?

Dependencies are added with br dep add <issue> <depends-on> after creating beads; follow schema → backend → UI ordering.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational