ralph-tui-create-beads_skill

This skill converts PRDs into beads for ralph-tui execution, generating an epic and child tasks 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

  • SKILL.md10.1 KB

Overview

This skill converts PRDs into a beads-based epic and child beads ready for ralph-tui execution. It extracts quality gates, creates an epic, turns each user story into a single bead with acceptance criteria (including quality gates), and wires dependencies so ralph-tui can run tasks autonomously. Output is written for the beads tracker and ready for bd create / bd dep add commands.

How this skill works

The skill parses the PRD (markdown or text) to find a Quality Gates section and the User Stories section. It generates a beads epic with child bead entries for each story, appends universal and UI-specific quality gates to acceptance criteria, and orders stories by dependency (schema → backend → UI). The skill emits bd create commands using single-quoted HEREDOC (<<'EOF') and bd dep add commands to record dependencies, and writes beads to .beads/beads.jsonl.

When to use it

  • You have a PRD and want ralph-tui to run tasks from beads.
  • You need an epic and per-story beads with verifiable acceptance criteria.
  • You want quality gates enforced for every story (typecheck, lint, etc.).
  • You need correct dependency ordering between schema, backend, and UI work.
  • You want bd create output ready for ralph-tui run --tracker beads.

Best practices

  • Ensure a clear Quality Gates section in the PRD or provide commands when prompted.
  • Split large features into small stories that finish in one agent iteration (2–3 sentence scope).
  • Order stories by dependencies: schema first, backend second, UI last.
  • Include explicit, verifiable acceptance criteria for each story before conversion.
  • Use single-quoted HEREDOC (<<'EOF') to avoid shell interpolation when creating beads.

Example use cases

  • Convert a PRD describing a new feature into an epic plus per-story beads for automated execution.
  • Add browser verification for UI stories by extracting UI gates from the PRD.
  • Split a large dashboard PRD into many small beads so each can be completed in one iteration.
  • Produce bd create and bd dep add commands to preserve dependency order for ralph-tui.

FAQ

The skill will ask which commands should pass or apply a sensible default such as npm run typecheck; you should confirm or provide required gates.

How does the skill decide dependencies and priorities?

It orders stories by type (schema → backend → UI) and then by document order, assigns higher priority to earlier dependencies, and emits bd dep add commands to enforce blocking relationships.

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