blueprint

Multi-session planning breaks complex tasks into 3–12 self-contained steps with dependency graphs for parallel or serial execution. It preserves context across agents and sessions by producing a self-contained plan file with per-step tasks, verification commands, and exit criteria.

You coordinate parallel steps and dependencies using a generated dependency graph within the construction plan. This graph structures the execution order, allowing fresh agents to execute self-contained steps serially or in parallel across multiple sessions.

Yes, you can validate plan quality and safety using a built-in adversarial review gate. This process checks the generated construction plan before execution to ensure the multi-session steps meet quality and safety standards.

A self-contained construction plan file includes per-step context, tasks, verification commands, and exit criteria. It provides everything a fresh agent needs to execute a specific step without requiring external session history.

You need a dependency graph for multi-session team coordination when managing complex tasks like migrations or refactors. It maps parallel and serial execution paths to ensure cross-session collaboration remains structured and context is preserved.