Our review
Compiles structured verification checklists from project requirements, supporting multiple types such as module completion, quality gates, and test coverage.
Strengths
- Supports six checklist types tailored to different project milestones
- Includes a mandatory RULE 14 compliance section to ensure requirement completeness
- Leverages standardized, priority-annotated, or dependency-ordered templates
- Outputs checklists ready to be written to docs or GitHub issues
Limitations
- Requires requirements documents (USER_REQUIREMENTS.md) to be available and up-to-date
- Depends on external reference files (checklist-types-reference.md, etc.) that must exist in the project
- Cannot auto-generate detailed acceptance criteria if not already specified in requirements
Use this skill when you need to create a formal verification checklist from written requirements to ensure quality and completeness of a module, review, or release.
Do not use it if requirements are informal or missing, or if a simple unstructured list suffices.
Security analysis
SafeThe skill only reads requirement documents and writes structured markdown checklists. No tools are declared and no executable commands are involved. It poses no risk of destructive actions, data exfiltration, or safety bypass.
No concerns found
Examples
Create a module completion checklist for the user authentication module based on USER_REQUIREMENTS.md. Include all verification points and a RULE 14 compliance section.Compile a release readiness checklist for version 2.0 using the release readiness type from checklist-types-reference.md. Write it to docs/release-checklist-v2.md.Generate a test coverage checklist for the payment API endpoints described in requirements. Use the test coverage template and ensure each item has clear acceptance criteria.name: amoa-checklist-compilation-patterns description: "Use when compiling verification checklists from requirements including module completion, quality gates, and test coverage checklists. Trigger with checklist compilation requests." license: Apache-2.0 compatibility: Requires AI Maestro installed. metadata: author: Emasoft version: 1.0.0 context: fork user-invocable: false agent: amoa-main
Checklist Compiler Skill
Overview
Compiles structured verification checklists from project requirements and specifications, supporting module completion, quality gates, test coverage, review, release readiness, and task assignment checklist types.
Prerequisites
- Access to requirements documentation (USER_REQUIREMENTS.md or similar)
- Understanding of module acceptance criteria
Instructions
- Read the requirements documentation
- Identify the checklist type needed (module completion, quality gate, review, test coverage, release readiness, or task assignment)
- Consult the appropriate reference document from Contents below
- Extract verification points and structure by logical groupings
- Define clear acceptance criteria for each item
- Add the mandatory RULE 14 compliance section
- Apply the appropriate template from checklist-templates.md
- Review for completeness, write to project docs or GitHub issue, and report results
Contents
Reference Documents
- checklist-types-reference.md - All 6 checklist types (module, quality gate, review, test coverage, release, task assignment)
- checklist-templates.md - Standard, priority-annotated, dependency-ordered, and test coverage templates
- checklist-compilation-workflow.md - 4-phase workflow: gather, structure, format, QA
- checklist-best-practices.md - Design principles, pitfalls, maintenance
- checklist-examples.md - Complete examples and walkthroughs
- skill-quick-reference.md - Inline examples, output deliverables, error handling, progress checklist
Quick Reference
| Type | Purpose | |------|---------| | Module Completion | Verify module ready for integration | | Quality Gate | Verify standards before progression | | Review | Conduct thorough code reviews | | Test Coverage | Ensure comprehensive test coverage | | Release Readiness | Verify release ready for deployment | | Task Assignment | Verify task properly defined |
Workflow: Requirements -> Extract Points -> Structure -> Define Criteria -> Format -> QA -> Write -> Report
RULE 14 Compliance
Every checklist MUST include:
## Requirement Compliance (RULE 14)
- [ ] USER_REQUIREMENTS.md exists and is current
- [ ] All user requirements addressed
- [ ] No technology substitutions without approval
- [ ] No scope reductions without approval
For inline examples, output deliverables, error handling, and progress tracking checklist, see: skill-quick-reference.md
Output
Produces a markdown checklist written to the project docs or a GitHub issue. Each checklist includes grouped verification items with acceptance criteria and a mandatory RULE 14 compliance section. See skill-quick-reference.md for output deliverables.
Examples
See checklist-examples.md for complete walkthroughs and skill-quick-reference.md for inline examples.
Error Handling
Missing requirements docs or unresolvable acceptance criteria halt compilation with a report to the orchestrator. See the error handling section in skill-quick-reference.md.
Resources
- checklist-types-reference.md
- checklist-templates.md
- checklist-compilation-workflow.md
- checklist-best-practices.md
- checklist-examples.md
- skill-quick-reference.md
Script Output Rules
All scripts invoked by this skill MUST follow the token-efficient output protocol:
- Verbose output goes to a timestamped report file in
docs_dev/reports/ - Stdout emits only 2-3 lines:
[OK/ERROR] script_name - summary+Report: path - Scripts accept
--output-dirto override the default report directory - EXCEPTION: Scripts in
scripts/amoa_stop_check/MUST output JSON to stdout (Claude Code hook requirement)
TDD Red-Green-Refactor
Testing
Skill that guides Claude through the complete TDD cycle.
Web Accessibility Audit
Testing
Performs a comprehensive web accessibility audit following WCAG standards.
UAT Test Case Generator
Testing
Generates structured and comprehensive user acceptance test cases.