بنقرة واحدة
ralph-init
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Token-efficient execution modifier with budget-aware routing
Kimi-native team worker protocol (ACK, mailbox, task lifecycle)
Persistence loop until task completion with verification
Architecture planning and plan approval workflow
Parallel agent execution via Kimi-native multi-worker runtime
Full autonomous execution from idea to working code
| name | ralph-init |
| description | Initialize a PRD (Product Requirements Document) for structured ralph-loop execution |
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution. Creates a structured requirements document that Ralph can use for goal-driven iteration.
/ralph-init "project or feature description"
.omk/plans/prd-{slug}.md with:
/ralph can use the PRD as its completion criteria.omk/state/{scope}/ralph-progress.json (session scope if active session exists).omk/plans/prd-{slug}.md..omk/state/{scope}/ralph-progress.json (session scope when available).--prd startup still validates machine-readable story state from .omk/prd.json..omk/prd.json / .omk/progress.txt inputs migrate one-way into canonical artifacts, but canonical PRD markdown is not yet the startup validation source for omx ralph --prd ....A structured PRD file saved to .omk/plans/ that serves as the definition of done for Ralph execution.
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.