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/openai-codex-prompting-2026.md
View on GitHub# OpenAI + Codex Prompting Notes (2026)
Last verified: March 6, 2026.
This file captures the prompt-engineering and model-selection assumptions used by `ralph-prompt-generator`.
Treat this as a secondary reference. Prompt improvement and constraint preservation come first; model or profile guidance only belongs in the final Ralph wrapper when it materially helps execution.
## Model Selection Defaults
- Codex sessions: prefer the current Codex default model unless the user explicitly wants a pinned model.
- As of March 6, 2026, the newest model powering Codex and Codex CLI is `gpt-5.4`.
- Pinning is optional; omit the model line when the current Codex default is sufficient.
- API-oriented runs: prefer `gpt-5-codex` when the user wants a pinned coding model.
- Use `gpt-5.4` instead when the workflow spans coding plus broader planning/writing tasks.
If the user explicitly requests a different model, preserve it.
## Reasoning Effort
If the final Ralph wrapper includes a `Reasoning effort: <medium|high|xhigh>` recommendation, use this guidance:
Guidance:
- `medium`: narrow, low-ambiguity tasks.
- `high`: multi-step engineering work.
- `xhigh`: ambiguous or high-risk work.
Notes:
- In Codex config, `model_reasoning_effort` exists and `xhigh` is model-dependent.
- In API reasoning best practices, OpenAI recommends direct prompts with clear delimiters and success criteria; avoid chain-of-thought prompting language.
## Prompting Rules To Enforce
- Keep prompts simple, direct, and explicit.
- Use strong delimiters (Markdown sections, XML tags) for instructions vs context.
- Define success criteria that are observable.
- Make validations explicit.
- Avoid "think step by step" / chain-of-thought style prompting.
- Start zero-shot; add examples only if they materially improve reliability.
## Where Reasoning Effort Gets Configured
Depending on the surface, reasoning effort may be set via Codex configuration.
Example (illustrative) profile-scoped config:
```toml
# ~/.codex/config.toml
[profiles.ralph_high]
model_reasoning_effort = "high"
[profiles.ralph_xhigh]
model_reasoning_effort = "xhigh"
```
If you use profiles, the generator can recommend `--profile ralph_high` / `--profile ralph_xhigh` in the final Ralph invocation snippet.
## Source Anchors
- [Codex Models](https://developers.openai.com/codex/models/)
- [Codex Config Reference](https://developers.openai.com/codex/config-reference/)
- [Codex Skills](https://developers.openai.com/codex/skills/)
- [Slash Commands in Codex CLI](https://developers.openai.com/codex/cli/slash-commands/)
- [Prompt Engineering Guide](https://platform.openai.com/docs/guides/prompt-engineering)
- [Reasoning Best Practices](https://platform.openai.com/docs/guides/reasoning-best-practices)
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 |