sdd-plan

To generate an execution plan for spec-driven development, you run the planning command after your research phase is approved, which automatically produces an execution_plan.md outlining tasks and verification strategies.

An execution_plan.md in SDD is a generated document that sequences development tasks with T-IDs, HITL/AFK markers, and rollback strategies to guide the execution phase following the research phase.

You sequence tasks with rollback strategies by automating the SDD planning phase, which assigns T-IDs and HITL/AFK markers to coordinate task ordering and define verification commands.

Yes, you need research and state documents from previous SDD phases before planning your execution phase, as the generated execution plan depends directly on approved prior research.

Yes, you can use this automated planning tool for trade-off analysis in task management, as it assists in making trade-off decisions for phase ordering and scope during execution plan generation.

The best way to automate the SDD planning phase without manual task sequencing is running the dedicated planning script, which automatically coordinates task ordering, verification commands, and rollback strategies into a markdown plan.