Results for “completion-claims”

Use when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Enforces code review practices: receiving feedback with technical rigor, requesting reviews via /code-review, and verifying before claiming completion.

Full autonomous engineering workflow

Archive accumulated phase directories from completed milestones

Makes completion state obvious at the end of every response using a red/yellow/green status block.

Validate built features through conversational UAT