Transform a simple prompt into a ralph-wiggum loop command with optional prompt improvement
Transforms your task description into a formatted ralph-wiggum loop command with optional prompt improvement, analysis, and saving. Use when you want to convert a simple idea into a detailed, executable agentic workflow.
/plugin marketplace add bennoloeffler/maude-claude-vunds-plugins/plugin install ralph-wiggum-helper@maude-claude-vunds-pluginsYou help the user create a properly formatted prompt for the ralph-wiggum agentic loop.
The user provides a multiline prompt <p> describing their task.
Before processing, ask these three questions. The user can answer individually OR use shortcuts:
Question 1:
Should I rework the prompt by analyzing your docs/code first to make it more specific and actionable? (Y/n)
Question 2:
Should I look for good "definition of done" criteria and improve the acceptance criteria in your prompt? (Y/n)
Question 3:
Should I save the original and improved prompt to
./docs/00_prompts/prompt-<feature>-ISO-DATE--HH-MM-SS.md? (Y/n)
Default is YES for all questions. Empty answer or "go" means yes.
If all answers are n/n/n:
If any answer is y:
For Question 1 = y:
For Question 2 = y:
For Question 3 = y:
mkdir -p ./docs/00_promptsprompt-<feature-slug>-YYYY-MM-DD--HH-MM-SS.mdEvery generated prompt MUST include these standard instructions (add them after the user's requirements but before the "Definition of Done"):
Instructions:
- Use command /feature-dev:feature-dev whenever useful
- Create general sub-agents when reading files, analysing files, creating code, running code, run tests, etc.
- Whenever you want to see results on monitor and find no other way: use command /screenshot in a general agent and get results back to work on them
You MUST output the prompt in TWO formats:
FORMAT 1: Human-Readable (for review)
Display the prompt nicely formatted with real line breaks, indentation, and structure. This is for the user to READ and UNDERSTAND what the task is.
š PROMPT (Human-Readable):
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Add dark mode support to SettingsView.swift
Requirements:
- Add a toggle in Settings for dark/light mode
- Store preference in SettingsStore (persist to ~/.maude/settings.json)
- Apply theme change immediately without app restart
- Follow existing UI patterns
Instructions:
- Use command /feature-dev:feature-dev whenever useful
- Create general sub-agents when reading files, analysing files, creating code, running code, run tests, etc.
- Whenever you want to see results on monitor and find no other way: use command /screenshot in a general agent and get results back to work on them
Definition of Done:
- [ ] Toggle appears in settings UI
- [ ] Preference persists across restarts
- [ ] Theme changes apply immediately
- [ ] Build succeeds with no warnings
When finished, say: <promise>TASK_COMPLETELY_DONE</promise>
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
FORMAT 2: Copy-Paste Command (single line with \n)
Convert ALL newlines to literal \n escape sequences.
This creates ONE LONG LINE that can be copied and pasted.
š COPY THIS COMMAND:
/ralph-wiggum:ralph-loop "Add dark mode support to SettingsView.swift\n\nRequirements:\n- Add a toggle in Settings for dark/light mode\n- Store preference in SettingsStore (persist to ~/.maude/settings.json)\n- Apply theme change immediately without app restart\n- Follow existing UI patterns\n\nInstructions:\n- Use command /feature-dev:feature-dev whenever useful\n- Create general sub-agents when reading files, analysing files, creating code, running code, run tests, etc.\n- Whenever you want to see results on monitor and find no other way: use command /screenshot in a general agent and get results back to work on them\n\nDefinition of Done:\n- [ ] Toggle appears in settings UI\n- [ ] Preference persists across restarts\n- [ ] Theme changes apply immediately\n- [ ] Build succeeds with no warnings\n\nWhen finished, say: <promise>TASK_COMPLETELY_DONE</promise>" --max-iterations 30 --completion-promise TASK_COMPLETELY_DONE
CRITICAL formatting rules for Format 2:
\n\n\n\"User input:
Add dark mode to the settings view
If n/n/n - Output:
š PROMPT (Human-Readable):
Add dark mode to the settings view.
Instructions:
- Use command /feature-dev:feature-dev whenever useful
- Create general sub-agents when reading files, analysing files, creating code, running code, run tests, etc.
- Whenever you want to see results on monitor and find no other way: use command /screenshot in a general agent and get results back to work on them
When finished, say: <promise>TASK_COMPLETELY_DONE</promise>
š COPY THIS COMMAND:
/ralph-wiggum:ralph-loop "Add dark mode to the settings view.\n\nInstructions:\n- Use command /feature-dev:feature-dev whenever useful\n- Create general sub-agents when reading files, analysing files, creating code, running code, run tests, etc.\n- Whenever you want to see results on monitor and find no other way: use command /screenshot in a general agent and get results back to work on them\n\nWhen finished, say: <promise>TASK_COMPLETELY_DONE</promise>" --max-iterations 30 --completion-promise TASK_COMPLETELY_DONE
If y/y/n - Output (after analysis):
š PROMPT (Human-Readable):
Add dark mode support to SettingsView.swift
Requirements:
- Add a toggle in Settings for dark/light mode
- Store preference in SettingsStore (persist to ~/.maude/settings.json)
- Apply theme change immediately without app restart
- Follow existing UI patterns
Instructions:
- Use command /feature-dev:feature-dev whenever useful
- Create general sub-agents when reading files, analysing files, creating code, running code, run tests, etc.
- Whenever you want to see results on monitor and find no other way: use command /screenshot in a general agent and get results back to work on them
Definition of Done:
- [ ] Toggle appears in settings UI
- [ ] Preference persists across restarts
- [ ] Theme changes apply immediately
- [ ] Build succeeds with no warnings
When finished, say: <promise>TASK_COMPLETELY_DONE</promise>
š COPY THIS COMMAND:
/ralph-wiggum:ralph-loop "Add dark mode support to SettingsView.swift\n\nRequirements:\n- Add a toggle in Settings for dark/light mode\n- Store preference in SettingsStore (persist to ~/.maude/settings.json)\n- Apply theme change immediately without app restart\n- Follow existing UI patterns\n\nInstructions:\n- Use command /feature-dev:feature-dev whenever useful\n- Create general sub-agents when reading files, analysing files, creating code, running code, run tests, etc.\n- Whenever you want to see results on monitor and find no other way: use command /screenshot in a general agent and get results back to work on them\n\nDefinition of Done:\n- [ ] Toggle appears in settings UI\n- [ ] Preference persists across restarts\n- [ ] Theme changes apply immediately\n- [ ] Build succeeds with no warnings\n\nWhen finished, say: <promise>TASK_COMPLETELY_DONE</promise>" --max-iterations 30 --completion-promise TASK_COMPLETELY_DONE