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.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-orchestrator-agentThis skill uses the workspace's default tool permissions.
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.mdCompiles verification checklists from project requirements using types like quality gates, reviews, test coverage, and release readiness. Triggers on checklist or verification requests.
Generates custom checklists to validate feature requirements for clarity, completeness, consistency, and coverage before implementation.
Creates structured quality gates for workflow boundaries like pre-merge checklists, deployments, and phase transitions with pass/fail criteria, exact commands, and escalation procedures.
Share bugs, ideas, or general feedback.
Comprehensive 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: