checklist-runner

Markdown checklist validation is automated by executing predefined .md checklists in autonomous mode to verify quality gates are met before a code push. The runner gathers contextual evidence from source code and test results to assess each checklist item.

Interactive quality assurance checklist execution is supported alongside autonomous YOLO mode. Running interactively allows you to facilitate structured review processes for development and DevOps tasks by stepping through validation items with contextual evidence gathering.

Evidence gathering for checklist validation automatically collects relevant project artifacts like story files, source code, and test results to assess checklist items. This contextual evidence collection ensures quality assurance checks are validated against actual project state.

Validating DevOps workflows with predefined checklists involves executing generic markdown-based checklists that support both autonomous and interactive modes. This approach ensures consistency and quality across various tasks and agents by automating the structured review process.

Checklist validation works for product ownership tasks in addition to development and DevOps workflows. The generic markdown-based checklist execution facilitates structured review processes across various tasks, gathering relevant documents and code to assess items.

Autonomous checklist validation mode should be avoided when you need to manually review contextual evidence or make subjective quality decisions. Interactive mode is better suited for facilitating structured review processes where human oversight is required for development tasks.