From codagent
Reviews implementation against task file requirements, checking every spec scenario and Done When criterion to identify gaps before shipping.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codagent:task-complianceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review the implementation against the task file(s). Extract every spec scenario (WHEN/THEN) and every Done When criterion, then verify each one was addressed. Report what's missing.
Review the implementation against the task file(s). Extract every spec scenario (WHEN/THEN) and every Done When criterion, then verify each one was addressed. Report what's missing.
From each task file, extract every:
This is your checklist. Every item must be accounted for.
For each checklist item, check whether the implementation addresses it.
Classify each item:
When you're unsure, read the actual code in the repository to verify before classifying. Do not mark something as missed without checking the code first.
Present your findings:
## Task Compliance
### Addressed
- [Scenario/criterion] — [evidence]
### Gaps
- [Scenario/criterion] — [what's missing or incomplete]
npx claudepluginhub codagent-ai/agent-skills --plugin codagentVerifies code implementations match specs, PRDs, epics, or tasks by checking completeness, acceptance criteria, edge cases, and scope creep. Use post- or during-implementation.
Reviews task-mapping.md and tasks.md for gaps in vertical slice completeness, TDD structure, story coverage, dependencies, and traceability; generates classified issues.
Verifies completed implementations for quality via subagents: completeness, test execution, code review, pragmatic review, production readiness, reality assessment. Compiles read-only reports.