Task Reviewer
Review task definitions for quality and INDEX.md consistency. This skill helps ensure tasks are well-defined before implementation begins.
When to Use
- •Before starting implementation of a task
- •After creating new tasks with
/pm:design - •When auditing task backlog quality
- •To find orphaned or mismatched tasks
Quick Review Process
- •Load configuration from
design.yamlto get repo prefix - •Scan tasks/ using
Globpattern:tasks/*-*/TASK.md(excludearchive/) - •Read each task's files: TASK.md, PROGRESS.md, REVIEW.md
- •Check against quality checklist (see checklist.md)
- •Validate INDEX.md against actual directories
- •Report findings with severity levels
Required Sections in TASK.md
Every task must have:
- •
# Task {PREFIX}-{NNN}: {Title}header - •
## Descriptionsection - •
## Dependenciessection (even if "None") - •
## User Storiessection (at least one) - •
## Files to Create/Modifysection - •
## Inventory Checksection - •
## Completion Criteriasection
Severity Levels
- •Critical: Task cannot be implemented (missing sections, invalid refs)
- •Warning: Quality issues (vague criteria, incomplete coverage)
- •Suggestion: Improvements recommended (better wording, more detail)
Common Issues
- •Vague acceptance criteria ("works correctly")
- •Missing error case coverage
- •Stale dependencies (completed tasks still blocking)
- •Incomplete file lists
- •Status mismatches between INDEX.md and TASK.md
- •Orphaned tasks (directory exists, not in INDEX.md)
For detailed checklist, see checklist.md. For output format template, see output-format.md.