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 .omq/plans/prd-{slug}.md with:
- Problem statement
- Goals and non-goals
- Acceptance criteria (testable)
- Technical constraints
- Implementation phases
Link to Ralph so that /ralph can use the PRD as its completion criteria
Initialize/ensure canonical progress ledger at .omq/state/{scope}/ralph-progress.json (session scope if active session exists)

Canonical source contract

Canonical PRD source of truth is .omq/plans/prd-{slug}.md.
Ralph progress source of truth is .omq/state/{scope}/ralph-progress.json (session scope when available).
Legacy .omq/prd.json / .omq/progress.txt inputs are compatibility-only and migrate one-way into canonical artifacts.

Output

A structured PRD file saved to .omq/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.

Más de este repositorio

mismo repositorio

doctor

chrisxue90/oh-my-qwencode

Diagnose and fix oh-my-qwencode installation issues

2026-04-032

help

chrisxue90/oh-my-qwencode

Guide on using oh-my-qwencode plugin

2026-04-032

analyze

chrisxue90/oh-my-qwencode

Run deep investigation of architecture, bugs, performance issues, or dependencies and return structured findings with file:line evidence. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs root cause analysis before making changes. Routes to architect agent or Qwen Code MCP for thorough cross-file reasoning.

2026-04-032

ask-claude

chrisxue90/oh-my-qwencode

Ask Claude via local CLI and capture a reusable artifact

2026-04-032

ask-gemini

chrisxue90/oh-my-qwencode

Ask Gemini via local CLI and capture a reusable artifact

2026-04-032

autopilot

chrisxue90/oh-my-qwencode

Full autonomous execution from idea to working code

2026-04-032

name	ralph-init
description	Initialize a PRD (Product Requirements Document) for structured ralph-loop execution

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 .omq/plans/prd-{slug}.md with:
- Problem statement
- Goals and non-goals
- Acceptance criteria (testable)
- Technical constraints
- Implementation phases
Link to Ralph so that /ralph can use the PRD as its completion criteria
Initialize/ensure canonical progress ledger at .omq/state/{scope}/ralph-progress.json (session scope if active session exists)

Canonical source contract

Canonical PRD source of truth is .omq/plans/prd-{slug}.md.
Ralph progress source of truth is .omq/state/{scope}/ralph-progress.json (session scope when available).
Legacy .omq/prd.json / .omq/progress.txt inputs are compatibility-only and migrate one-way into canonical artifacts.

Output

A structured PRD file saved to .omq/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.