Oh-my-codex ralph-init
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution
install
source · Clone the upstream repo
git clone https://github.com/Yeachan-Heo/oh-my-codex
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/Yeachan-Heo/oh-my-codex "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/ralph-init" ~/.claude/skills/yeachan-heo-oh-my-codex-ralph-init && rm -rf "$T"
manifest:
skills/ralph-init/SKILL.mdsource content
Ralph Init
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution. Creates a structured requirements document that Ralph can use for goal-driven iteration.
Usage
/ralph-init "project or feature description"
Behavior
- Gather requirements via interactive interview or from the provided description
- Create PRD at
with:.omx/plans/prd-{slug}.md- Problem statement
- Goals and non-goals
- Acceptance criteria (testable)
- Technical constraints
- Implementation phases
- Link to Ralph so that
can use the PRD as its completion criteria/ralph - Initialize/ensure canonical progress ledger at
(session scope if active session exists).omx/state/{scope}/ralph-progress.json
Canonical source contract
- Canonical PRD source of truth is
..omx/plans/prd-{slug}.md - Ralph progress source of truth is
(session scope when available)..omx/state/{scope}/ralph-progress.json - During the current compatibility window, Ralph
startup still validates machine-readable story state from--prd
..omx/prd.json - Legacy
/.omx/prd.json
inputs migrate one-way into canonical artifacts, but canonical PRD markdown is not yet the startup validation source for.omx/progress.txt
.omx ralph --prd ...
Output
A structured PRD file saved to
.omx/plans/ that serves as the definition of done for Ralph execution.
Next Steps
After creating the PRD, start execution with:
/ralph "implement the PRD"
Ralph will iterate until all acceptance criteria in the PRD are met and architect-verified.