amoa-checklist-compilation-patterns
Use when compiling verification checklists from requirements. Trigger with checklist or verification requests. Loaded by ai-maestro-orchestrator-agent-main-agent
Best use case
amoa-checklist-compilation-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when compiling verification checklists from requirements. Trigger with checklist or verification requests. Loaded by ai-maestro-orchestrator-agent-main-agent
Teams using amoa-checklist-compilation-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/amoa-checklist-compilation-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How amoa-checklist-compilation-patterns Compares
| Feature / Agent | amoa-checklist-compilation-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when compiling verification checklists from requirements. Trigger with checklist or verification requests. Loaded by ai-maestro-orchestrator-agent-main-agent
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Checklist Compiler Skill ## Overview Compiles verification checklists from project requirements. ## Prerequisites - Access to USER_REQUIREMENTS.md ## Instructions 1. Read requirements and identify checklist type needed 2. Consult the appropriate reference from Contents below 3. Extract verification points, structure by groups, define acceptance criteria 4. Apply template from checklist-templates.md, append RULE 14 section, and output Copy this checklist and track your progress: - [ ] Read requirements and identify checklist type - [ ] Extract verification points and define criteria - [ ] Apply template, append RULE 14 section - [ ] Write to project docs or GitHub issue ## Contents 1. [checklist-types-reference.md](references/checklist-types-reference.md) <!-- TOC: Module Completion Checklists | Quality Gate Checklists | Review Checklists | Test Coverage Checklists | Release Readiness Checklists | Task Assignment Checklists | Checklist Type Selection Guide --> 2. [checklist-templates.md](references/checklist-templates.md) <!-- TOC: Standard Checklist Template | Priority-Annotated Checklist Template | Dependency-Ordered Checklist Template | Test Coverage Checklist Template --> 3. [checklist-compilation-workflow.md](references/checklist-compilation-workflow.md) <!-- TOC: Phase 1: Requirements Gathering | Phase 2: Checklist Structuring | Phase 3: Format and Document | Phase 4: Quality Assurance | Step-by-Step Procedure --> 4. [checklist-best-practices.md](references/checklist-best-practices.md) <!-- TOC: Checklist Design Principles | Common Pitfalls to Avoid | Checklist Maintenance --> 5. [checklist-examples.md](references/checklist-examples.md) <!-- TOC: Checklist Compilation Examples | Table of Contents | Complete Example: SVG Parser Quality Gate Checklist | Scenario and Requirements | Compiled Checklist Document | Prerequisites | Section 1: Implementation Completeness | Section 2: Test Coverage and Pass Rate | Section 3: Code Quality | Section 4: Documentation | Section 5: Security | Completion Criteria | Sign-Off | Compilation Process Walkthrough | Reading Requirements | Identifying Verification Points | Structuring the Checklist | Writing the Document | Orchestrator Interaction Example | Request from Orchestrator | Completion Report Format --> 6. [skill-quick-reference.md](references/skill-quick-reference.md) <!-- TOC: Inline Examples | Output Deliverables | Error Handling | Progress Tracking Checklist --> ## Examples **Input:** "Compile a quality gate checklist for auth-core" **Output:** Checklist at project docs/checklists/ directory (e.g., auth-core-quality-gate.md) with grouped items, criteria, RULE 14 section. See checklist-examples.md in Contents above for walkthroughs. ## Error Handling - Missing requirements: halt with `[ERROR] No USER_REQUIREMENTS.md found` - Ambiguous criteria: flag and request clarification - Incomplete modules: partial checklist with `[PENDING]` markers ## Output Markdown checklist with grouped items, criteria, and RULE 14 section. ## Resources See Contents section above for all reference files.
Related Skills
amoa-verification-patterns
Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-two-phase-mode
Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-task-distribution
Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-remote-agent-coordinator
Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-progress-monitoring
Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-plan-phase
Use when running Plan Phase of two-phase mode. Trigger with planning, requirements, or plan approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-orchestration-patterns
Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-orchestration-loop
Use when running the orchestrator loop or managing stop hook behavior. Trigger with loop, stop hook, or state file requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-module-sync
Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-module-management
Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-module-lifecycle
Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent
amoa-messaging-templates
Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent