zero-debt

Enforce immediate, complete, and systematic fixes for technical debt during code reviews.

Updated Jun 3, 2026

Search Tags:#refactoring #maintenance #standards #code-quality #best-practices #software-engineering #zero-debt

Ready to run

npx skills add https://github.com/mgreenly/ikigai --skill zero-debt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: zero-debt
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/zero-debt
Command: npx skills add https://github.com/mgreenly/ikigai --skill zero-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zero Technical Debt aims to reduce long-term maintenance costs by enforcing immediate, complete, and systematic fixes to defects and standard violations.

Core Features & Use Cases

Immediate fixes: Fix defects and standards violations as soon as they are discovered.
Root-cause & consistency: Address root causes and ensure consistent patterns across the codebase.
Use cases: Sprint cleanups, code reviews, onboarding new engineers, and maintaining long-term stability.

Quick Start

Audit the current module for a debt issue and fix it immediately, completely, and systematically within your current task.

Frequently Asked Questions about zero-debt

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

FAQPage Schema

How do I eliminate technical debt during routine code maintenance?▼

Eliminate technical debt during code maintenance by enforcing immediate, complete, and systematic fixes that address the root cause, ensure pattern consistency, and document changes according to project standards.

What is the best way to handle code quality issues discovered during a sprint cleanup?▼

Handle code quality issues during sprint cleanups by fixing defects and standards violations immediately upon discovery, addressing root causes to maintain long-term codebase stability rather than applying temporary patches.

How does a systematic refactoring approach ensure consistency across modules?▼

Systematic refactoring ensures consistency across modules by enforcing a three-step protocol: fixing the defect's root cause, aligning code with consistent naming conventions and error handling patterns, and documenting all changes.

Can I use disciplined maintenance practices to help onboard new engineers?▼

Yes, you can use disciplined maintenance practices to onboard new engineers by having them audit modules for debt issues and apply systematic fixes, which teaches project standards and consistent error handling patterns through immediate action.

Why should technical debt be fixed immediately rather than deferred to a later sprint?▼

Technical debt should be fixed immediately to reduce long-term maintenance costs and prevent defects from propagating, ensuring root causes are addressed and consistent patterns are maintained across the codebase without delay.