ralph▌

Convert PRDs to executable beads for ralph-tui using beads-rust CLI. \n \n Extracts quality gates from PRD and appends them to every story's acceptance criteria \n Creates an epic with right-sized child beads (one story per bead, completable in a single agent iteration) \n Establishes dependencies between beads using br dep add to enforce execution order (schema → backend → UI) \n Outputs br create and br dep add commands with safe HEREDOC syntax for special characters \n Syncs beads to .beads/

Automated agent-driven development loop that executes AI agents against user story acceptance criteria. \n \n Structures features as JSON-formatted user stories with testable acceptance criteria that agents can verify and track \n Runs AI agents in a continuous loop to implement features, check acceptance criteria, and log progress for subsequent agent iterations \n Requires prerequisite setup of AI coding agent configuration and user stories framework before running the Ralph agent loop \n Inte

[RALPH + ULTRAWORK - ITERATION {{ITERATION}}/{{MAX}}]

Converts existing PRDs to the prd.json format that Ralph uses for autonomous execution.

Spec-driven autonomous AI coding with fresh context per task using iterative bash loops. \n \n Implements Geoffrey Huntley's methodology where each loop iteration starts a new agent process with a clean context window, preventing degradation over long sessions \n Requires clear, testable acceptance criteria in specification files; agent outputs <promise>DONE</promise> only when all criteria are verified and tests pass \n Maintains shared state on disk via specs/ , ralph_history.txt , a

Convert PRDs to beads (epic + child tasks) for ralph-tui autonomous execution. \n \n Extracts quality gates from PRD and appends them to every bead's acceptance criteria, ensuring consistent validation across all stories \n Creates an epic with right-sized child beads, where each story is completable in a single ralph-tui iteration without context overflow \n Establishes dependencies between beads using bd dep add to enforce correct execution order: schema → backend → UI → integration \n Outputs

Convert PRDs to prd.json format for ralph-tui autonomous execution. \n \n Extracts quality gates (universal and UI-specific commands) from PRD and appends them to every story's acceptance criteria \n Outputs a flat JSON structure with \"name\" and \"userStories\" at root level, ready for ralph-tui run --prd <path> \n Enforces right-sized stories completable in one agent iteration; splits oversized work into schema, backend, and UI layers \n Sets up story dependencies via dependsOn array to

Generate detailed Product Requirements Documents optimized for AI agent execution via ralph-tui task orchestration. \n \n Guides users through adaptive clarifying questions to understand feature scope, goals, and quality requirements \n Produces structured PRDs with user stories, functional requirements, and explicit quality gates for automated conversion to beads issues or prd.json \n Emphasizes small, independently completable user stories with verifiable acceptance criteria suitable for singl

You are a planning assistant that helps users create well-structured ralph-loop commands. Your goal is to collaborate with the user to produce a focused, actionable ralph command with clear sections.

$22