ralph-orchestrator

---

name: ralph-orchestrator description: Orchestrates the full Ralph autonomous agent pipeline from requirements gathering to execution. Use when building new features, platforms, or complex tasks that need structured development through spec-interview, PRD generation, and autonomous implementation. model: claude-opus-4-5 context: fork

1. spec-interview → Gather comprehensive requirements through guided discovery
2. generate-prd → Create actionable Product Requirements Document
3. ralph-convert-prd → Transform PRD into atomic user stories (prd.json)
4. ralph.sh → Execute autonomous implementation loop

This skill coordinates these tools while keeping you in control at decision points.

<essential_principles>

Never assume Ralph "remembers" previous iterations.

Right-sized:

• Add a database column
• Create a UI component
• Update a server action
• Implement a filter

Too large (will fail):

• Build entire dashboard
• Add authentication system
• Refactor entire API

Broken code compounds across iterations. Never skip quality checks.

Don't rush. Bad requirements = wasted iterations.

</essential_principles>

1. Full pipeline - Start from scratch (spec → PRD → prd.json → execute)
2. Continue from PRD - Already have PRD, convert and execute
3. Execute only - Already have prd.json, run Ralph
4. Check status - View current prd.json progress

Wait for response before proceeding.

After reading the workflow, follow it exactly.

<quick_reference>

Key Files:

Commands:

Copy# Run Ralph from your project directory
# (assumes toolkit is at ~/projects/claude-code-toolkit)
~/projects/claude-code-toolkit/skills/ralph-orchestrator/scripts/ralph.sh

# Or create an alias in ~/.bashrc:
alias ralph='~/projects/claude-code-toolkit/skills/ralph-orchestrator/scripts/ralph.sh'

# Run with custom iteration limit
ralph 5

# Check story status
cat prd.json | jq '.userStories[] | {id, title, passes}'

# View learnings
cat progress.txt

</quick_reference>

<workflows_index>

<success_criteria> Pipeline is complete when:

• Requirements gathered through spec-interview
• PRD created with verifiable acceptance criteria
• prd.json has atomic, right-sized stories
• All stories have passes: true in prd.json
• Code committed and quality checks passing </success_criteria>