microtask-decomposition

Task decomposition breaks complex development tasks into atomic, single-file microtasks from your tasks.md. This manages dependencies and execution phases for granular implementation and parallelization, making large features easier to organize.

Dependency mapping identifies microtasks that can execute in parallel, speeding up overall development time. It breaks down complex workflows into atomic actions and visualizes dependencies to enable structured execution across independent files.

Yes, task decomposition supports agile development by organizing code into granular, independently executable microtasks. It targets single files or functions, making complex multi-faceted features manageable within structured execution phases.

Decomposing an authentication system creates atomic microtasks for database schema, user model, endpoints, password reset service, email verification, session management, UI components, and integration tests, each targeting a single file.

No specific workflow management tool is required. The decomposition process relies on a tasks.md file as input, breaking down multi-faceted tasks into atomic, independently executable microtasks without external dependencies.

Avoid atomic microtask decomposition for simple, single-file modifications that do not benefit from dependency mapping or parallel execution. It is designed for complex, multi-faceted tasks requiring granular implementation and progress tracking.