theflixerbox77/ralph-wiggum-codex / skills/ralph-prompt-generator
ralph-prompt-generator
VerifiedUse when a user has a rough prompt that needs a staged prompt-improvement workflow for `$ralph-wiggum-codex`, with saved draft/final files and explicit review checkpoints.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.6 KB |
| agents/openai.yaml | config | 605 B |
| references/openai-codex-prompting-2026.md | markdown | 2.7 KB |
| references/prompt-improver-principles.md | markdown | 2.4 KB |
| references/prompt-improver-workflow-codex.md | markdown | 3.6 KB |
| references/ralph-flag-selection-matrix.md | markdown | 3.7 KB |
references/prompt-improver-principles.md
View on GitHub# Prompt Improver Principles
Curated principles for turning rough prompts into staged, repo-backed improvements for `ralph-prompt-generator`.
## Source Basis
Distilled from the prompt-improver workflows:
- `prompt-improver.md` (analysis + draft)
- `prompt-improver-finalize.md` (critique + revision + polish)
## Core Rule
Clarify, do not prescribe.
The generator improves task framing, constraints, and verification criteria. It should not pre-complete work that the downstream coding agent should discover or implement.
## Workflow Posture
- Prompt improvement comes first; Ralph-specific config comes last.
- Save planning, draft, and final outputs in the repo-backed prompt-improver workspace.
- Reuse earlier artifacts during later phases instead of redoing analysis from scratch.
- Pause at explicit review checkpoints after Steps 1-2 and after Step 4.
## Rewrite Checklist (Practical)
1. Make the objective testable.
- Convert vague goals into concrete targets.
- Prefer one primary objective; split unrelated asks into separate runs.
2. Preserve constraints and intent.
- Copy explicit must/must-not rules.
- Do not "helpfully" relax constraints.
3. Add non-goals.
- When the user prompt is broad, add 2-5 non-goals to prevent drift.
4. Define success criteria.
- Prefer criteria that map to validations.
- If success is subjective, ask for an objective proxy.
5. Use delimiters.
- Separate objective, constraints, validations, and settings.
- Keep the prompt readable and scannable.
## Anti-Patterns
Do not:
- Provide filled-in example outputs that are effectively the answer.
- Prescribe step-by-step execution details (tools, commands, file edits) unless the user explicitly requested an implementation plan.
- Add extra deliverables (reports, dashboards, docs) that were not asked for.
- Inflate the prompt with generic "be thorough" language when it doesn't change execution.
## Clarification Heuristic
Ask questions only when ambiguity changes execution behavior:
- Missing `cwd` / target repo
- Missing validation commands
- Missing scope (what files are allowed to change)
- Conflicting requirements
- No measurable success criteria
If ambiguity is non-critical, proceed with explicit assumptions.
## Final Ralph Wrapper Policy
When the prompt itself is finished:
- point `$ralph-wiggum-codex` at the saved production-ready prompt file
- add model or flag guidance only when it materially improves the run
- keep the wrapper short; do not restate the full prompt inline
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |