task-dag-decomposition

What problem does it solve?

It prevents multi-step software changes from breaking in integration by replacing vague “do this then that” plans with an explicit, dependency-aware task DAG that supports verification and safe rollback.

Core Features & Use Cases

• Dependency-ordered DAG decomposition: Breaks changes into dependency-ordered tasks with clear directional edges so execution order is unambiguous.
• Parallel-safe file-scope ownership: Assigns tasks into parallel groups where allowed-file scopes don’t overlap, reducing merge conflicts in multi-agent work.
• Verification + done conditions per task: Requires each task to define checkable verification criteria and a concrete done condition before successors begin.
• Migration and rollback sequencing guardrails: Enforces safety-critical ordering (e.g., schema before ORM forward, ORM compatibility before rollback) and requires rollback/recovery notes for runtime-behavior tasks.
• Rollback-aware task records: Documents what is irreversible, how rollback is performed, and who triggers recovery for reviewer scrutiny.

Quick Start

Use the task-dag-decomposition capability to decompose your change into a dependency-ordered, parallel-safe DAG with explicit verification and rollback notes.