ralph-new

Creating an autonomous task involves generating a uniquely identified task directory, prompting for task descriptions and verification methods, and defining a plan.md file to guide execution. This ensures tasks are properly structured and organized before running.

A plan.md file defines task details, success criteria, and test commands for autonomous execution. It serves as the central reference document that outlines what the task needs to accomplish and how to verify its completion.

Enforcing safety guidelines during autonomous task execution requires setting up and maintaining a guardrails.md file. This file establishes consistent task execution policies to ensure processes adhere to defined safety and operational boundaries.

When creating a new autonomous task, you need to provide a task description and verification methods. If these are not supplied initially, the system will interactively prompt you to gather the necessary information before generating the task.

Autonomous execution tasks are organized within a structured task directory system, creating uniquely identified folders such as .ralph/ralph-N. This directory structure ensures each task has its own isolated workspace for plan files and execution data.

Yes, custom test commands can be defined within the plan.md file when creating a task. These commands act as the success criteria, allowing the autonomous execution system to verify whether the task has been completed correctly.