Results for “claim-validation”

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.

Validate built features through conversational UAT

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

Select evidence-bearing context for a downstream consumer after work when claims, artifacts, validation, unresolved decisions, or omissions must cross a boundary.