Individual skill

zero-tech-debt

Refactor a feature toward its intended product architecture, removing obsolete flows and unnecessary abstractions while preserving required behavior and contracts. Use when a structural redesign or tech-debt cleanup is requested. Trigger with "refactor properly", "remove legacy" or "zero-tech-debt"; use a focused patch for hotfixes and security backports.

skills/.curated/zero-tech-debt/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Zero Tech Debt

## Overview

Build toward the intended product shape rather than preserving the sequence of
historical patches. Keep one coherent end state in scope. Remove obsolete layers
when evidence supports removal; do not use smaller diffs or fewer files as a
substitute for the requested architecture.

Current code is evidence of behavior and contracts, not automatic architectural
authority. Explicit requirements, supported clients, persisted data, security
boundaries and the user's instructions still govern what may change.

## Prerequisites
Back to top