From emasoft-orchestrator-agent
Use when compiling verification checklists from requirements including module completion, quality gates, and test coverage checklists. Trigger with checklist compilation requests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/emasoft-orchestrator-agent:eoa-checklist-compilation-patternsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive patterns and templates for compiling verification checklists from requirements and specifications.
README.mdreferences/checklist-best-practices.mdreferences/checklist-compilation-workflow.mdreferences/checklist-examples.mdreferences/checklist-templates.mdreferences/checklist-types-reference.mdreferences/op-add-rule14-section.mdreferences/op-compile-module-completion-checklist.mdreferences/op-compile-quality-gate-checklist.mdreferences/op-compile-release-readiness-checklist.mdreferences/op-compile-review-checklist.mdreferences/op-compile-task-assignment-checklist.mdreferences/op-compile-test-coverage-checklist.mdComprehensive patterns and templates for compiling verification checklists from requirements and specifications.
checklist-compilation-workflow.md
| Type | Purpose | Key Elements |
|---|---|---|
| Module Completion | Verify module ready for integration | Implementation, docs, tests, types |
| Quality Gate | Verify standards before progression | Metrics, coverage, linting, security |
| Review | Conduct thorough code reviews | Structure, naming, resources, tests |
| Test Coverage | Ensure comprehensive test coverage | Unit, integration, edge cases |
| Release Readiness | Verify release ready for deployment | Features, docs, versioning, rollback |
| Task Assignment | Verify task properly defined | Objectives, criteria, constraints |
Requirements → Extract Points → Structure → Define Criteria → Format → QA → Write → Report
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
## Module: auth-core Completion Checklist
### Implementation
- [ ] All acceptance criteria implemented
- [ ] No TODO comments remaining
- [ ] Error handling complete
### Testing
- [ ] Unit tests pass (80%+ coverage)
- [ ] Integration tests pass
- [ ] Edge cases covered
### Documentation
- [ ] API documentation updated
- [ ] README updated if needed
- [ ] Changelog entry added
## Quality Gate: Pre-Merge
- [ ] All tests passing
- [ ] Coverage >= 80%
- [ ] No linting errors
- [ ] Type checks pass
- [ ] Security scan clean
- [ ] 4 verification loops completed
This skill produces the following deliverables:
| Deliverable | Format | Location | Description |
|---|---|---|---|
| Compiled Checklist | Markdown | Project docs or issue | Verification checklist compiled from requirements |
| Checklist Report | Markdown | Agent output | Summary of compilation process and checklist structure |
| Quality Assurance | Inline | Checklist document | RULE 14 compliance section and verification steps |
| Issue | Cause | Solution |
|---|---|---|
| Missing requirements | USER_REQUIREMENTS.md not created | Create requirements file first |
| Incomplete checklist | Acceptance criteria unclear | Request clarification from user |
| Checklist too large | Requirements too broad | Break into smaller modules |
Copy this checklist and track your progress:
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-orchestrator-agentCompiles verification checklists from project requirements. Reads USER_REQUIREMENTS.md, extracts verification points, applies structured templates with priority and dependency ordering, and outputs formatted checklists.
Generates custom checklists for validating requirements quality (clarity, completeness, consistency) within active workflows. Useful for ensuring specs are ready for implementation.
Generates custom checklists to validate requirement quality (completeness, clarity, consistency) from specifications and user input. Use for requirement validation or specification completeness checks.