checklist-runner

To automate a Definition of Done check, you validate work against a specified Markdown checklist to produce a structured approval decision. The process yields consistent PASS, FAIL, PARTIAL, or N/A verdicts with per-item evidence reasoning.

Enforcing a pre-push quality gate involves running a checklist validation that collects git diff context, code files, and test results. This systematically checks your changes against defined criteria to compute pass rates and explicit fix recommendations.

Yes, you can run checklist validation autonomously using deterministic YOLO mode. This mode executes the entire Markdown checklist without human intervention, while an alternative interactive mode prompts section-by-section for manual confirmation.

Checklist validation gathers evidence for release readiness through context-aware loading. It automatically collects story files, code files, test results, and git diff context as specified by the Markdown checklist to support per-item verdicts.

You need an interactive section-by-section review for PO validation when assessing change impact requires human confirmation. This mode prompts reviewers sequentially through checklist sections to ensure accurate validation of complex evidence.