checklist-runner
Checklist Runner
Generic checklist execution engine. Validates work against any .md checklist with consistent behavior across all agents.
Usage
/checklist-runner story-dod-checklist
/checklist-runner pre-push-checklist --mode yolo
/checklist-runner po-master-checklist --mode interactive
Execution
1. Resolve Checklist
Parse $ARGUMENTS for checklist name. Search in order:
.aiox-core/development/checklists/{name}.md.aiox-core/development/checklists/{name}- Fuzzy match if exact not found (e.g., "dod" → "story-dod-checklist.md")
If no checklist specified or multiple matches, present numbered options list.
2. Determine Mode
| Mode | Behavior |
|---|---|
yolo (default) |
Process all sections autonomously, present final report |
interactive |
Section-by-section with user confirmation between each |
3. Load Context
Gather documents and artifacts specified at the top of the checklist:
- Story files from
docs/stories/ - Source code files from story's File List
- Test results from last
npm testrun - Git diff for current changes
4. Process Checklist Items
For each item in the checklist:
- Read and understand the requirement
- Look for evidence in documentation/code that satisfies it
- Consider both explicit mentions and implicit coverage
- Follow any embedded LLM instructions in the checklist
Mark each item:
| Verdict | Symbol | Meaning |
|---|---|---|
| PASS | ✅ | Requirement clearly met |
| FAIL | ❌ | Requirement not met or insufficient |
| PARTIAL | ⚠️ | Some aspects covered, needs improvement |
| N/A | ➖ | Not applicable (with justification) |
5. Section Summary
For each section calculate:
- Pass rate:
(PASS count) / (total - N/A count) * 100 - Common themes in failed items
- Specific recommendations for improvement
6. Final Report
## Checklist Report: {checklist-name}
**Date:** {YYYY-MM-DD}
**Agent:** {current agent}
**Mode:** {yolo|interactive}
### Summary
| Section | Items | Pass | Fail | Partial | N/A | Rate |
|---------|-------|------|------|---------|-----|------|
| ... | ... | ... | ... | ... | ... | ...% |
**Overall:** {PASS_RATE}% ({total_pass}/{total_applicable})
### Failed Items
1. **{item}** — {reason} → {recommendation}
### Decision
**{APPROVED | NEEDS_WORK | FAIL}**
- APPROVED: >= 90% pass rate, 0 FAIL on critical items
- NEEDS_WORK: 70-89% pass rate OR any FAIL on non-critical
- FAIL: < 70% pass rate OR any FAIL on critical items
Available Checklists
| Checklist | Used By | Purpose |
|---|---|---|
story-dod-checklist.md |
@dev | Definition of Done for stories |
self-critique-checklist.md |
@dev | Self-review at implementation checkpoints |
pre-push-checklist.md |
@devops | Quality gate before git push |
release-checklist.md |
@devops | Release readiness verification |
po-master-checklist.md |
@po | PO validation checklist |
change-checklist.md |
@po | Change impact assessment |
More from synkraai/aios-core
aiox-po
Product Owner (Pax). Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
1aiox-dev
Full Stack Developer (Dex). Use for code implementation, debugging, refactoring, and development best practices
1aiox-qa
Test Architect & Quality Advisor (Quinn). Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requ...
1synapse
This skill should be used when users want to understand the SYNAPSE context engine, manage domains, configure context rules, or troubleshoot rule injection. Use when asked about SYNAPSE architecture, domain management, star-commands, context brackets, or the 8-layer processing pipeline.
1aiox-pm
Product Manager (Morgan). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roa...
1aiox-sm
Scrum Master (River). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlo...
1