ralph-init

To generate a Product Requirements Document, this Skill creates a prd.json file that defines project scope, branch names, descriptions, and user stories based on a provided task description. It ensures stories are right-sized, verifiable, and independent for structured execution.

Breaking down a feature task into verifiable user stories is done by providing a task description to this Skill, which then parses the input and outputs a structured prd.json file. It adheres to guidelines ensuring each story is right-sized and independent.

Progress tracking during ralph-loop execution works by initializing a progress.txt file alongside the PRD. This log file is created at setup to continuously record and monitor the execution status of the defined user stories throughout the project lifecycle.

No dependencies or external components are required to initialize a PRD. The Skill operates independently to generate the necessary .omc/prd.json and .omc/progress.txt files directly from your provided task description without needing additional setup.

You can use this initialization for software engineering tasks that require structured workflow execution. By inputting a task description like implementing OAuth2 authentication, it generates the required PRD and progress log to prepare the project for the ralph-loop framework.

You should initialize a PRD before starting feature development to automate the creation of essential files and ensure a standardized, organized workflow. It breaks down the overall task into well-defined user stories and sets up a progress log for efficient execution tracking.