write-task-todo

To convert task analysis into a structured todo document, the skill generates a single docs/todolist.md file. This file captures evolving definitions, interfaces, tests, and implementation slices using [x]/[ ] markers to guide multi-loop execution.

A loop-contracted review process is a multi-stage engineering workflow mechanism that coordinates task execution through defined loop contracts. It ensures structured review cycles guide implementation tasks after initial alignment is achieved.

To maintain canonical documentation while tracking tasks, the approach uses a definitions-first method. It ensures canonical docs remain the source of truth, while the generated todolist.md references these definitions rather than duplicating them.

Yes, you can use a single todolist.md file for multi-loop implementation tasks. The workflow enforces a single working file at docs/todolist.md to capture evolving definitions, interfaces, tests, and execution slices throughout the project lifecycle.

The best way to prepare a docs/todolist.md after task alignment is to populate it with an initial set of [x]/[ ] items following the defined structure. This creates a clear execution plan with alignment artifacts for multi-loop implementation.

You need a definitions-first approach for task analysis todos when large tasks require clear definitions, tests, and execution slices. It ensures canonical docs remain the source of truth and that todos reference them accurately during multi-loop implementation.