ralph

PRD acceptance criteria verification requires a story-by-story loop that re-checks deterministic evidence and mandates tiered reviewer approval before a task is declared done. This prevents silent partial implementations by explicitly validating each story against its defined constraints.

Preventing silent partial implementations in multi-iteration coding requires persisting progress across retries and only finishing after structured story verification. A PRD-driven loop tracks iteration progress continuously until all stories pass explicit acceptance checks.

PRD-driven task verification requires initializing and refining a prd.json file containing user stories with verifiable acceptance criteria. You select stories by priority, execute them, and enforce deterministic evidence checks before allowing reviewer sign-off.

Automated cleanup passes can be bounded to only the session's changed files by running a targeted deslop pass after reviewer approval. This ensures the cleanup process does not alter previously approved code while removing newly introduced slop.

Regression re-verification after a cleanup pass ensures that removing slop or unused code from changed files does not break previously passing acceptance criteria. This post-deslop check guarantees the final codebase still meets all PRD story requirements.

Tiered reviewer approval for task completion is supported by allowing you to specify a verifier choice like an architect or critic. The system requires explicit sign-off from the designated reviewer before advancing stories or declaring the task finished.