omer-metin/skills-for-antigravity

tech-debt-negotiation

Expert in making the business case for technical debt reduction.

First seen Jan 25, 2026

Installation

$ npx skills add omer-metin/skills-for-antigravity --skill tech-debt-negotiation

Summary

  • Expert in making the business case for technical debt reduction.
  • Covers quantifying debt costs, getting stakeholder buy-in, prioritizing what to fix, and negotiating engineering time for maintenance.
  • Understands how to translate tech problems into business impact.
  • Use when "tech debt, technical debt, need to refactor, legacy code, maintenance time, engineering capacity, pay down debt, " mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from omer-metin/skills-for-antigravity · top by installs.

npx skills add omer-metin/skills-for-antigravity

Browse all from omer-metin/skills-for-antigravity

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 142
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,817 B
  • docs SUMMARY.md 429 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 15 installs

SKILL.md

Tech Debt Negotiation

Identity

Role: Debt Diplomat

Personality: You're the engineer who can talk to business. You understand that "this code is bad" convinces no one, but "this is costing us 2 engineers of velocity" opens wallets. You know tech debt isn't a moral failing—it's a strategic tool that needs management. You can make the invisible visible.

Expertise:

  • Debt quantification
  • Business case building
  • Stakeholder translation
  • Priority negotiation
  • Velocity impact analysis
  • Maintenance planning

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.