Overview
AIOX checklists are quality gate validation frameworks used by agents to ensure work meets standards before proceeding. Checklists are markdown files with structured validation criteria, organized by domain and purpose.string
.aiox-core/development/checklists/- Development checklists.aiox-core/product/checklists/- Product/quality checklists
string
Markdown with checkbox lists and validation instructions
string
Quality gates for tasks, stories, and releases
Checklist Categories
Development Checklists
checklist
Location:
.aiox-core/development/checklists/Purpose: Validate agent definition quality before releaseCategories:- Agent metadata completeness
- Persona profile validation
- Command structure verification
- Dependency integrity
- Documentation quality
- Voice DNA authenticity
checklist
Purpose: Validate AIOX compatibility with existing (brownfield) projectsValidates:
- Existing project structure
- Technology stack compatibility
- Integration points
- Migration path clarity
- Risk assessment
checklist
Purpose: Audit agent memory file quality and completenessValidates:
- Memory file structure
- Entry completeness
- Pattern validity
- Gotcha accuracy
- Decision log integrity
checklist
Purpose: Mandatory self-review for Coder Agent (ADE workflow)Used in: Steps 5.5 & 6.5 of 13-step subtask executionValidates:
- Code quality
- Requirements alignment
- Edge case handling
- Error scenarios
- Test coverage
- Documentation updates
Product Checklists
checklist
Location:
.aiox-core/product/checklists/Purpose: Comprehensive architecture validation frameworkSections:- Requirements Alignment
- Architecture Fundamentals
- Technical Stack & Decisions
- Frontend Design & Implementation (if applicable)
- Resilience & Operational Readiness
- Security & Compliance
- Implementation Guidance
- Dependency & Integration Management
- AI Agent Implementation Suitability
- Accessibility Implementation (frontend only)
- Section-by-section (interactive)
- All-at-once (comprehensive)
checklist
Purpose: Validate React/TypeScript component qualityCategories:
- Code Quality (TypeScript, props, types)
- Styling (Tailwind, variants, dark mode)
- Accessibility (WCAG AA, ARIA, keyboard)
- Testing (unit, integration, coverage ≥85%)
- Documentation (component docs, examples)
- Storybook (if enabled)
checklist
Purpose: Database schema design validationValidates:
- Schema design patterns
- Normalization level
- Index strategy
- RLS (Row-Level Security) policies
- Migration integrity
- Performance considerations
checklist
Purpose: WCAG 2.2 AA compliance validationValidates:
- Semantic HTML
- ARIA attributes
- Keyboard navigation
- Focus management
- Color contrast (WCAG & APCA)
- Screen reader compatibility
checklist
Purpose: Validate changes before commit/mergeCategories:
- Code review items
- Test coverage
- Breaking changes
- Documentation updates
- Backward compatibility
Checklist Structure
Checklists follow a standard format:Checklist Metadata
string
required
One-line description of what the checklist validatesExample:
"Validate component before marking complete"string
Primary agent responsible for checklist executionExample:
"Atlas (Design System Builder)", "Quinn (QA Specialist)"string
Quality standard being enforcedExample:
"Production-ready React/TypeScript components", "WCAG 2.2 AA"Validation Criteria Format
Basic Criteria
format
Detailed Criteria
format
Conditional Criteria
format
LLM Instructions
format
Checklist Execution
Manual Execution
Developers execute checklists manually:- Open checklist file
- Work through each criterion
- Check boxes as validated
- Note any failures or concerns
- Complete reviewer/date fields
- Mark overall PASS/FAIL
Agent Execution
Agents execute checklists programmatically:Integration with Tasks
Checklists are invoked by tasks:Quality Gates
concept
A quality gate is a checkpoint that must pass before proceedingImplementation:
- Checklist defines criteria
- Agent validates all items
- Gate passes only if all criteria met
- On failure: Block progression, provide report
Quality Gate Standards
gate
Agent Quality Gate - All agents must pass before releaseValidates:
- 300+ lines of content
- Voice DNA authenticity
- Output examples included
- Command loader present
- Task files exist
- Maturity level ≥ Nivel 2
gate
Story Definition of Done - All stories must pass before reviewValidates:
- All tasks completed
- Tests passing
- Documentation updated
- File list complete
- No regression failures
Advanced Checklist Features
Project Type Detection
Evidence-Based Validation
Execution Modes
Final Report Generation
Checklist Best Practices
Checklist Design
Checklist Design
- Keep criteria clear and actionable
- Provide validation methods
- Group related items into sections
- Include LLM instructions for AI agents
- Support conditional validation
- Define clear pass/fail criteria
Validation Criteria
Validation Criteria
- Make criteria measurable
- Avoid subjective judgments
- Provide examples where helpful
- Include specific thresholds (e.g., “≥85% coverage”)
- Reference standards (e.g., “WCAG 2.2 AA”)
Agent Integration
Agent Integration
- Use [[LLM: …]] blocks for agent guidance
- Provide context and reasoning
- Include validation examples
- Define report format expectations
- Support both manual and automated execution
Maintenance
Maintenance
- Review checklists after each usage
- Update based on team feedback
- Add new criteria as standards evolve
- Remove obsolete criteria
- Version checklists when making changes
Creating Custom Checklists
-
Choose location:
-
Define structure:
-
Register with agent:
-
Integrate with task:
Related Documentation
Reference:
.aiox-core/development/checklists/ and .aiox-core/product/checklists/