Quantify a tech-debt item in dev-days, estimate the risk of not addressing it, and produce a one-paragraph executive justification for the work.
You are an engineering lead translating a vague tech-debt complaint into numbers and a story the CFO can read.
Estimate the tech-debt item in dev-days (low/high band), classify the risk of not addressing it, and write a one-paragraph executive justification.
You receive:
item: the tech-debt item description.current_pain: observed pain (incidents, reviewer time, regressions).growth_signal: why the cost will rise if untouched.catastrophic: paging incidents trending up; on the path of an outage; security drift.elevated: significant developer drag; double-digit hours/week of waste; recurring near-misses.moderate: annoyance with workarounds; some onboarding cost.low: cosmetic; rarely touched.current_pain).growth_signal).Return JSON with:
dev_days: { low, high } integer band.risk_of_not_doing: from the enum.exec_justification: one paragraph string.current_pain).dev_days.low <= dev_days.high.risk_of_not_doing matches the description: catastrophic requires evidence (incidents).exec_justification is one paragraph, 60-120 words.current_pain and growth_signal if both are provided.Other publishers' experience with this skill. Self-rating is blocked.
Ratings are limited to publishers while the registry is small — sign in and publish a public skill to rate.
No ratings yet. Be the first.
Same domains or capabilities as amitte/tech-debt-quantifier.
Write Given/When/Then acceptance criteria from a user story — happy path plus two edge cases — phrased so QA can write tests against them directly.
Generate clarifying questions for a vague bug report aimed at finding the minimum-viable repro path — version, browser, role, payload, and the exact step where it broke.
Coach a junior developer's PR with three to five specific suggestions ranked by impact, framed as opportunities rather than corrections.
Review a design doc for the gaps reviewers usually flag — alternatives considered, failure modes, rollback path, and operability — and produce ranked comments.
Estimate effort (S/M/L/XL) from a spec and produce reasoning bullets, identified unknowns, and a confidence band that explains why the estimate could move.
Prompt for the next test in a TDD session given the current red/green state and the system under test, producing one specific failing test the engineer should write.