d-plan-fix

Generate an executable fix plan from a root-cause analysis document.

Updated Jan 22, 2026

Search Tags:#automation #planning #debugging #fix #plan #root-cause #gtd

Ready to run

npx skills add https://github.com/Hoang604/get-thing-done --skill d-plan-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: d-plan-fix
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/d-plan-fix
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill d-plan-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts verified root-cause analyses into concise, executable fix plans that specify 2-3 atomic tasks, clear completion criteria, and rollback guidance.

Core Features & Use Cases

Generates a FIX_PLAN.md from ROOT_CAUSE.md with a 2-3 task structure.
Embeds root-cause references and affected files into the plan to ensure traceability.
Provides a safety-focused template with constraints, verification criteria, and rollback guidance for controlled execution.

Quick Start

Run the d-plan-fix skill after you have a ROOT_CAUSE.md to generate FIX_PLAN.md.

Frequently Asked Questions about d-plan-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an executable fix plan from a root cause analysis?▼

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.

What is the best way to structure a debugging fix plan to ensure safe execution?▼

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.

Do I need a verified root cause document before creating a fix plan?▼

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.

How to turn root causes into atomic tasks with done criteria and a rollback plan?▼

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.

Why should I exclude implementation code from my fix plan?▼

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.

Can I trace affected files directly within my generated fix plan?▼

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.