decompose

To decompose tests into atomic tasks for parallel execution, you provide a feature identifier to generate a task map. This map groups discrete tasks into a wave-based DAG, preserving dependencies while maximizing parallelism across unit, integration, and end-to-end suites.

A wave-based DAG is a directed acyclic graph that groups atomic test tasks into execution waves. It organizes tasks so that independent ones run in parallel within the same wave, while strictly respecting dependency boundaries to accelerate feedback loops.

You generate module stewardship artifacts by analyzing feature-driven tests and creating an AGENT.md file per module. This process also builds a module-graph and compiles a tasks document to clarify ownership boundaries and track sprint progress.

Yes, task decomposition applies to feature-driven test suites across unit, integration, and end-to-end levels. It atomizes these tests into discrete tasks with explicit inputs, outputs, and completion criteria to drive sprint planning and automation workflows.

The best way to track progress for decomposed test tasks is to compile a comprehensive tasks document. This document maps the atomic tasks, wave-based execution order, and module stewardship boundaries generated during the decomposition process.

Yes, test decomposition works without external dependencies. You simply provide a feature identifier like F001 to generate a complete decomposition plan and task DAG, organizing tests into atomic tasks with clear inputs and outputs.