zero-debt

Identify and eliminate technical debt with immediate, complete, systematic fixes.

Updated Mar 4, 2026

Search Tags:#refactoring #code-quality #quality-assurance #root-cause-analysis #technical-debt #zero-debt #established-patterns

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zero Technical Debt philosophy and work style principles for ikigai, guiding teams to fix issues immediately, completely, and systematically to maintain sustainable code health and maintainability.

Core Features & Use Cases

Immediate fixes: Fix defects on discovery to prevent debt accumulation.
Root-cause focus: Address root causes rather than symptoms.
Follow established patterns: Ensure consistency with project conventions.

Quick Start

Apply the zero-debt principle to fix any discovered deficiency 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 ongoing code development?▼

To eliminate technical debt during ongoing development, fix discovered defects immediately, completely, and systematically within your current task to prevent debt accumulation and maintain code health.

What is the best way to address root causes instead of symptoms during refactoring?▼

Addressing root causes during refactoring requires systematic fixes that enforce consistency with established project patterns, ensuring the underlying defect is resolved rather than just treating surface symptoms.

How do I enforce code quality and established patterns during code reviews?▼

Enforce code quality during reviews by applying systematic fixes that align code with established project conventions, ensuring any discovered deficiency is resolved completely before approval.

When do I need architectural approval to fix technical debt systematically?▼

Architectural approval to fix technical debt is only necessary when systematic fixes deviate from established project guidelines, allowing immediate root-cause resolution without unnecessary overhead.

Can I apply zero technical debt principles to general maintenance tasks?▼

You can apply zero technical debt principles to general maintenance tasks by enforcing immediate, complete fixes that satisfy project quality standards and prevent further deficiency accumulation.