modules/programs/agents/shared/_archive/ralph-prep/SKILL.md
Full Ralph preparation workflow - create spec skeleton, interview to flesh out, and generate docs PRD for Ralph story-loop execution. Triggers on "ralph prep", "prep ralph", "prepare for ralph", "set up ralph for".
npx skillsauth add MichaelVessia/nixos-config ralph-prepInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Orchestrate complete Ralph preparation: spec creation, interview, and docs PRD generation for story-loop execution.
The user provides a feature description. Extract a short kebab-case name from it for file naming.
Examples: auth-refactor, integration-tests, spotify-integration
User input: $ARGUMENTS
Use AskUserQuestion:
Do you have an existing spec, or should we create one?
Options:
- "Create new spec" (recommended)
- "Use existing spec" (provide path)
Gather initial context with AskUserQuestion:
Round 1 - What:
What feature/initiative is this?
Options:
- [User describes in "Other"]
Round 2 - Why & Scope:
Questions (multi-select where appropriate):
1. What problem does this solve?
2. What's explicitly OUT of scope?
3. Any Jira ticket or reference doc?
Create specs/{FEATURE_NAME}.md with structure:
# {Feature Name} Spec
## Overview
**Jira:** [TICKET-ID](link)
{Problem statement from interview}
## Success Criteria
- [ ] {Extracted from answers}
## Out of Scope
- {From answers}
## Phase 1: {TBD}
### {Section}
{Placeholder - to be fleshed out}
### Phase 1 Checkpoint
- [ ] TBD
## Verification Commands
```bash
# TBD
### 4. Call spec-interview
Invoke the spec-interview skill to flesh out the skeleton:
Skill: spec-interview Args: specs/{FEATURE_NAME}.md
Wait for spec-interview to complete its interview process.
### 5. Verify Ralph Infrastructure
Check ralph setup exists:
- `ralph/ralph.sh` executable
- `ralph/prd.json` exists
- `ralph/RALPH_PROMPT.md` exists
- `ralph/scripts/prd-status.sh` exists
If missing, inform user:
Ralph infrastructure not found. See ralph/HOW_TO_RALPH.md for setup.
### 6. Call write-a-prd
Convert the completed spec to a docs PRD:
Skill: write-a-prd Args: specs/{FEATURE_NAME}.md docs
### 7. Final Summary
Ralph preparation complete!
Spec: specs/{FEATURE_NAME}.md PRD: docs/prds/{FEATURE_NAME}.md
Commands:
## Error Handling
If user cancels during spec creation:
- Save partial progress
- Inform user they can resume with `/spec-interview specs/{file}.md`
development
Restate the last message in plain human language, with no jargon.
testing
Fan out a batch of work items into one PR each via isolated worktree agents, review every PR before it opens, then babysit all PRs through green CI and review feedback. Use when the user wants to fan out PRs, dispatch parallel PR agents over a list of items, or run a batch of independent changes as separate PRs.
development
Dispatch user-visible coding or research agents through Herdr with Codex-Desktop-like thread ergonomics. Use when the user asks to use Herdr to spawn, dispatch, fan out, inspect, follow up with, or monitor agent workspaces/threads.
development
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.