spec-tasks

Task decomposition breaks complex software designs into ordered, atomic tasks with explicit dependencies, ensuring each task yields a single binary acceptance test for independent verification and clear rollback criteria.

Acceptance criteria in task decomposition workflows require each atomic task to yield a single binary acceptance test, providing explicit validation, artifact naming conventions, and clear rollback conditions to verify task completion.

Tracking dependencies in task decomposition involves generating ordered, atomic tasks with explicit dependency mapping, ensuring each task is independently verifiable and satisfies project-management requirements for artifact naming and budgeting.

Yes, task decomposition is applied to design-to-task workflows where multiple atomic tasks are created with explicit dependencies. It handles complex designs by enforcing single binary acceptance tests and clear rollback criteria for each task.

Using task templates for specs involves creating the initial Task N from a predefined template and committing the result to the repository. The output artifact follows the `.claude/specs/<id>/tasks.md` naming convention.

Atomic task decomposition may be unnecessary for simple design work lacking multiple dependencies. If your project does not require explicit artifact naming conventions or single binary acceptance tests, this structured decomposition adds overhead.