ralph-init

Structuring product requirements into right-sized stories involves creating a formal PRD with acceptance criteria and priority ordering so autonomous build runs start with clear, verifiable goals. This skill scaffolds that process by generating the required project files.

Tracking progress before launching a ralph-loop workflow requires writing a progress log with start timestamps, pattern notes, and status markers. This establishes verifiable progress records that replace ad-hoc planning and track story completion.

Scaffolding a PRD for ralph-loop execution involves creating a JSON file that captures the project, branch naming, summary, and user stories with acceptance criteria like passing typechecks and tests. This enforces story discipline and independent validation.

Yes, product leads can use this tool to break down active tasks into ordered user stories and log baseline progress expectations before kicking off an autonomous build request. It ensures each story is right-sized and independent for focused sessions.

Product planning with this tool requires emitting specific JSON and TXT files in an .omd directory to store the PRD and progress log. These files capture user stories, acceptance criteria, and timestamps needed to begin the loop.