checklist-runner

You can validate completed work against a Markdown checklist by running an automated validation that evaluates each item against provided documents, diffs, and test results to produce deterministic PASS, FAIL, PARTIAL, or N/A verdicts.

Evidence-driven checklist validation for story acceptance is a process that evaluates checklist items using provided documents, artifacts, and embedded instructions, then summarizes pass rates and recommendations for product owner validation.

Yes, you can run pre-push quality gates autonomously without manual review by executing checklists in YOLO mode, which performs a full validation run across all items automatically.

Configuring pass rates and critical items for a release readiness check allows the validation process to generate a final decision based on your specific rules, summarizing section outcomes and overall readiness.

Yes, documentation validation supports interactive step-by-step review, allowing you to evaluate checklist items sequentially with confirmations rather than running the entire validation autonomously.

Automated checklist validation for CI readiness is limited to evaluating available evidence such as Markdown checklists, code, diffs, and test results, meaning it cannot verify items lacking accessible documentation or artifacts.