Autonomous development orchestrator that combines ephemeral Ralph workers with Beads granular task tracking. Use when executing multiple beads autonomously, running parallel development tasks, or when you need persistent work tracking across sessions.
Orchestrates autonomous development by spawning ephemeral agents to execute granular tracked tasks.
/plugin marketplace add DuncanJurman/entropy-plugins/plugin install god-ralph@entropy-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/BEAD_SPEC.mdreferences/WORKFLOWS.mdgod-ralph is an autonomous development system that combines two powerful patterns:
Use god-ralph when:
Each Ralph worker:
Persistent agent that:
bd readyAfter each merge:
| Command | Purpose |
|---|---|
/god-ralph start | Start autonomous execution (dry-run first) |
/god-ralph plan | Interactive wizard to create beads |
/god-ralph status | Show current progress |
/god-ralph stop | Gracefully stop execution |
/god-ralph <id> | Run Ralph on specific bead |
For god-ralph to work effectively, beads should include:
title: "Clear, actionable title"
description: "Detailed description"
type: feature|task|bug
priority: 0-4
# In comments until schema supports:
ralph_spec:
completion_promise: "BEAD COMPLETE"
max_iterations: 50
acceptance_criteria:
- type: test
command: "npm test"
- type: lint
command: "npm run lint"
# 1. Plan your work
/god-ralph plan
# Wizard asks questions, creates beads
# 2. Review what's ready
bd ready
# 3. Start autonomous execution
/god-ralph start
# Shows dry-run plan, asks for confirmation
# 4. Monitor progress
/god-ralph status
# 5. Stop when needed
/god-ralph stop
god-ralph automatically parallelizes independent beads:
Group 1 (parallel):
- beads-abc: "Add API endpoint" → worktree/1
- beads-def: "Add frontend page" → worktree/2
Group 2 (after Group 1):
- beads-ghi: "Integration tests" → worktree/3
Beads with file overlap run sequentially.
Each Ralph works in a separate git worktree:
Main repo: /project/ → main
Worktree 1: .worktrees/ralph-1/ → ralph/beads-abc
Worktree 2: .worktrees/ralph-2/ → ralph/beads-def
This allows:
Typical costs:
/god-ralph status shows running cost estimate.
When things go wrong:
Ralph fails (max iterations)
Merge conflict
Verification fails
god-ralph extends the beads ecosystem:
# Create beads normally
bd create --title="..." --type=feature
# Add ralph_spec via comments
bd comments <id> --add "ralph_spec: ..."
# god-ralph uses bd CLI under the hood
bd ready # Find work
bd update # Claim work
bd close # Complete work
bd dep # Manage dependencies
/god-ralph status periodicallyThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.