Technical Debt

Workflow

1. Describe the concrete delay, defect risk or operating cost caused by the debt.
2. Compare the smallest repair with a larger refactor; prioritize frequent and costly changes.
3. Add a behavioral safety check before restructuring a risky path.
4. Track only actionable repayment work with an owner and trigger; do not create a speculative debt inventory.

Completion

Return the concrete result, verification evidence and any material unresolved limitation. Keep documentation proportional to the change and preserve human feedback.

Focused references

• Detailed examples: load only the section relevant to the task.

---

Canonical source: skills/project-management/technical-debt.md.