realize

Project plan partitioning divides an approved plan into loop-safe tasks for autonomous execution and human-supervised tasks requiring manual oversight. It classifies tasks based on atomicity, isolatability, testability, invariant awareness, and decision avoidance, writing loop-safe items into a backlog file.

A loop-safe task meets specific classification criteria including atomicity, isolatability, testability, invariant awareness, and decision avoidance. These properties ensure the task can execute autonomously within a loop without requiring human intervention or encountering ambiguous decision points.

Yes, creating a partitioned backlog requires existing loop scaffolding to be in place. The task partitioning process defers to superpowers when present, relying on the established scaffolding to safely manage the loop-safe tasks written into the backlog file.

Task classification in backlog management separates human-supervised tasks from loop-safe tasks by evaluating decision avoidance and isolatability. Tasks requiring manual oversight are identified during partitioning and excluded from the loop-safe backlog file intended for automated execution.

Yes, you can use this for any approved software project plan reaching a phase where a subset of tasks can be automated. It processes the approved plan as input to generate the partitioned backlog, ensuring the plan is ready for loop execution.

You should avoid automated task partitioning when your approved plan lacks established loop scaffolding or involves tasks that cannot meet criteria for atomicity, isolatability, and testability, as these conditions are required to safely separate loop-safe execution from human-supervised oversight.