You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
NewMaintained
Automatic
◆Coding pack
Last verified 8/29/2026
What it changes
Passed 6 of 22 test cases with the skill, and 17 of 22 without it.
Without skill75%
With skill25%
Checks it passed that the model alone missed
Provides product user stories, functional requirements, and UI mockups for the feature
1 fixed18 passed either way0 still failing3 broke
Pass-rate lift
-50 pp
Tokens
+40%
Agent turns
0%
Response time
+31%
Model gemini-3.6-flashMeasured 8/29/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Write a complete functional product requirements document (PRD) for adding a new social media sharing and user tagging feature to our mobile application.
What was checked, without and with the skill
Checked
Without skill
With skill
Provides product user stories, functional requirements, and UI mockups for the feature
Missed
Passed
Does not turn the request into a technical debt inventory or code audit exercise
Passed
Passed
case-20 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md32 linessingle file
Technical Debt Analysis and Remediation
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.
Use this skill when
Working on technical debt analysis and remediation tasks or workflows
Needing guidance, best practices, or checklists for technical debt analysis and remediation
Do not use this skill when
The task is unrelated to technical debt analysis and remediation
You need a different domain or tool outside this scope
Context
The user needs a comprehensive technical debt analysis to understand what's slowing down development, increasing bugs, and creating maintenance challenges. Focus on practical, measurable improvements with clear ROI.