Stats
Actions
Tags
From ralph
Interactive wizard generates Product Requirements Document (PRD), Ralph autonomous loop setup, task sets, and project structure from discovery questions. For /create-prd or project initialization.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ralph:ralph-prdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactive wizard to create Product Requirements Document and Ralph project setup with task sets.
Interactive wizard to create Product Requirements Document and Ralph project setup with task sets.
/create-prd # Start interactive wizard
/create-prd "Build a todo app" # Start with description
project/
├── PROMPT.md # Instructions for each iteration
├── ralph.sh # Loop runner (executable)
└── .ralph/
├── current-taskset -> tasksets/initial # Symlink to active taskset
└── tasksets/
└── initial/ # Your task set (named during setup)
├── tasks.json # Task list (JSON)
├── prd.md # Requirements (Markdown)
├── memories.md # Persistent learnings
├── config.json # Ralph settings
└── activity.log # Iteration log (empty)
Ask these discovery questions:
When discovery questions involve deleting files, removing dependencies, or other destructive changes:
See EXAMPLES.md for vague-vs-specific anti-patterns.
Convert features into atomic tasks with categories: setup, feature, integration, styling, testing, verification. See WORKFLOW.md for task format and categories.
Final verification task: Always include a final task with verificationTier: "visual" (UI projects) or "api" (API-only projects) that verifies the complete application works end-to-end. This catches issues that individual task verification misses.
See WORKFLOW.md for detailed discovery flow.
See EXAMPLES.md for PRD examples.
See TROUBLESHOOTING.md for common issues.
You MUST read and use these templates when generating output files. Do NOT write simplified versions from memory — the loop depends on exact field names and signal formats.
prompt.md.template - CRITICAL: Contains the RALPH_COMPLETE: signal in Step 5. Read this template with the Read tool and fill in {{placeholders}}. Never hand-write PROMPT.md.tasks.json.template - CRITICAL: Tasks use "passes": false / "passes": true (NOT "status": "pending" / "status": "done"). The completion signal checks passes.prd.md.template - PRD document structureconfig.json.template - Ralph configurationmemories.md.template - Learnings fileThe ralph.sh loop script checks for RALPH_COMPLETE: in the output to stop. The prompt.md.template Step 5 tells Ralph to emit this signal when all tasks have passes: true. If PROMPT.md is hand-written without Step 5, or tasks.json uses a different field name, the loop runs forever.
Always copy ralph.sh from this plugin's scripts/ralph.sh directory. It contains required flags (--dangerously-skip-permissions, --disallowedTools) that are essential for non-interactive execution.
./ralph.sh 20 # Start autonomous loop
After initial setup, create more task sets:
/ralph taskset new "auth-feature" # Create new task set
/ralph taskset list # See all task sets
/ralph taskset switch "auth-feature" # Switch to it
npx claudepluginhub joaquimscosta/arkhe-claude-plugins --plugin ralphGenerates Product Requirements Documents (PRDs) for new features via phased approach: discovery, codebase exploration with agents, clarifying questions. Useful for feature planning or project starts.
Ralph autonomous agent for iterative development with multi-PRD parallel support. Commands: '/ralph-ryan:prd' (create PRD), '/ralph-ryan:prep' (prepare), '/ralph-ryan:run' (execute), '/ralph-ryan:status' (overview). Triggers on: ralph prd, ralph prep, ralph run, ralph go, ralph status.
Generates structured PROMPT.md files for autonomous AI workflows (Ralph Loops) from rough descriptions or PRDs, with phases, validation criteria, completion promises, and blind review.