maestro:verification

Prevent premature completion claims by mandating an evidence-based verification protocol that requires running build, test, and lint commands before committing. Reviewing their output proves correctness and stability.

Evidence-based verification is a protocol requiring concrete proof of correctness through executed build, test, and lint outputs. It addresses dishonest work status claims by mandating output review before reporting tasks or features as done.

Verify regressions before merging by running build, test, and lint commands, then reviewing their output. This protocol ensures all acceptance criteria are met and confirms code stability before claiming completion.

Yes, the verification protocol supports multi-scope checking by providing distinct verification checklists for individual tasks, development phases, and entire features. This ensures comprehensive evidence-based validation across all project levels.

Run lint and test commands before pull requests to enforce commit hygiene and prevent unsubstantiated claims of work status. Reviewing command output provides concrete proof of correctness and confirms no regressions were introduced.

Yes, you can use this verification process for CI/CD regression checks. It mandates running build and test commands while reviewing their output to ensure stability and prevent regressions before claiming any work is complete.