review-tasks

To validate task dependencies and traceability in a graph.yml file, parse the task model to verify explicit dependencies, map tasks to requirements, and ensure coverage from design components to declared tasks.

Checking task breakdowns for clear acceptance criteria involves analyzing each declared task to enforce single-responsibility, validate scope, and ensure explicit acceptance criteria are present for actionable work.

Reviewing task completeness for declared requirements requires mapping tasks to design documents and requirements, analyzing the graph-based task model to surface gaps, and enforcing quality gates for full coverage.

Yes, you can validate task breakdowns without external dependencies by invoking the skill directly with the repository root or the path to the .gid/graph.yml file to analyze declared tasks.

Task breakdowns often result in blocked work and misaligned expectations due to unclear scope and missing dependencies, which requires validating clarity and enforcing explicit reads and writes between tasks.

You need to enforce quality gates on your task management graph when task breakdowns become unclear, requiring analysis of every declared task to surface gaps, ensure traceability, and validate single-responsibility.