task-decomposition

Task decomposition breaks macro-tasks into atomic micro-tasks that can be completed in a single session by generating structured documents for tasks.md, micro-tasks.md, and decisions.md to maintain clear planning and decision history.

Maintaining decision history during service development uses template documents like decisions.md to record choices, while tasks.md and micro-tasks.md track the decomposed atomic steps needed for consistent and auditable project planning.

Generating task decomposition templates requires providing a macro-task, which triggers the creation of structured tasks.md, micro-tasks.md, and decisions.md files to establish the supporting documentation structure for your workflow.

Task decomposition can flag security-relevant steps for downstream review routing, ensuring that micro-tasks touching sensitive areas within the project planning workflow are properly identified for security checks.

Atomic task decomposition works without external dependencies, relying solely on providing a macro-task input to generate the initial tasks.md, micro-tasks.md, and decisions.md templates for structured documentation.

You need to decompose tasks into atomic micro-tasks when clear task breakdown and decision history are required for project planning and service development workflows to ensure auditability and consistent implementation.