d-plan-fix

To generate a fix plan from a root cause analysis, you need a verified root cause document. The plan defines 2-3 atomic tasks, explicit done criteria, and a rollback plan without embedding implementation code.

A safe debugging fix plan structure includes 2-3 atomic tasks, clear completion verification criteria, and rollback guidance. It embeds root-cause references and affected files for traceability during controlled execution.

Yes, you need a verified root cause document at .gtd/debug/current/ROOT_CAUSE.md before creating a fix plan. This ensures the generated plan targets the actual issue and includes appropriate rollback guidance.

Turning root causes into atomic tasks requires extracting the verified issue and defining 2-3 specific actionable steps. Each plan must include explicit done criteria and a rollback plan while excluding implementation code.

Excluding implementation code from a fix plan ensures the document remains a controlled execution strategy. It focuses on defining atomic tasks, done criteria, and rollback guidance rather than acting as a code script.

Yes, the generated fix plan embeds root-cause references and affected files directly into the document. This ensures full traceability from the original debugging analysis to the final executable tasks.