ralph

To ensure task completion, use a PRD-driven persistence loop that structures work into user stories with testable acceptance criteria and iterates until every user story passes verification. This mechanism prevents partial implementations and missed steps by requiring reviewer sign-off.

A PRD-driven persistence loop is a task management mechanism that structures work into user stories with testable acceptance criteria. It continuously iterates on a task until every user story passes acceptance criteria and receives reviewer sign-off.

To initialize a task using the PRD-driven persistence loop, run the command `oms-prd init <task-description>`. This command sets up the structured task tracking required to enforce user story verification and reviewer sign-off.

Yes, you need OMS orchestration tools and PRD setup to track user story acceptance criteria. The persistence loop requires OMS and oms-prd dependencies to manage structured task tracking and enforce iterative verification.

Use a persistence loop for software development tasks that require guaranteed completion and verification, such as complex projects with multiple user stories. It is ideal for scenarios where preventing partial implementations and missed steps is critical.

Iterative verification prevents missed steps by keeping the task active in a persistence loop until every user story passes its acceptance criteria and receives reviewer sign-off. This ensures no partial implementations are accepted before the task is marked complete.