task-planning-shrimp

To plan multi-step work for a multi-file refactor, you can create a parent objective with child tasks and leaves, mapping dependencies and blocking items to enforce small task sizes. It outputs created task links plus the immediate next action to execute.

The best way to track dependencies in a project task tree is to create a parent-child task structure that explicitly marks dependencies and blocking items. This enforces atomic task sizes and outputs the next action to execute.

You need structured task planning for migrations when breaking down complex, long-running projects into atomic steps with acceptance criteria. It creates a clear audit trail of decisions and maps dependencies to prevent blockers during multi-file refactors.

Yes, you can generate the immediate next task from a concise project objective by creating a task tree. The system outputs created task links plus the next action to execute, enforcing small task sizes for long-running work.