reversa-to-do

Roadmap decomposition breaks feature items into atomic actions with sequential stable IDs and explicit dependency mapping. This process organizes actions into standard phase tables and marks parallel execution tasks with indicators to produce a checkable to-do plan.

Atomic tasks are single-turn, coherent actions requiring no mid-execution human feedback. You should use atomic task decomposition when you need to transform a feature roadmap into small, well-scoped implementation units with clear dependencies.

To generate an actions file, the system reads your roadmap file and applies standard before-to-do hooks. It transforms the roadmap into a structured actions file with phase-based tables, parallelism markers, and stable task IDs before writing the output atomically.

Yes, task decomposition supports parallel execution by marking independent tasks with parallelism indicators. It organizes actions by standard phases, allowing teams to identify and run simultaneous tasks while maintaining stable IDs and dependency mapping.

Yes, you need a roadmap file and standard state configuration files. The decomposition process validates required files, reads the state configuration, and applies standard before-to-do and after-to-do hooks to generate the executable actions file.