skills.rest
tachyon-beep
tachyon-beepCOMMUNITY
Explore all skills by this author →
GitHub

identifying-technical-debt

Catalog prioritized technical debt items with explicit scope and delivery dates.

1|Updated Oct 29, 2025
Search Tags:#documentation#technical debt#time management#prioritization#cataloging#execution discipline
One-click install
npx skills add https://github.com/tachyon-beep/hamlet --skill identifying-technical-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: identifying-technical-debt
Source: https://github.com/tachyon-beep/hamlet/tree/main/.claude/skills/axiom-system-architect/skills/identifying-technical-debt
Command: npx skills add https://github.com/tachyon-beep/hamlet --skill identifying-technical-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces execution discipline for cataloging technical debt under time pressure, ensuring deliverable documents arrive first and explanations follow.

Core Features & Use Cases

  • Partial delivery with explicit limitations: produce a structured partial catalog (X items analyzed) and note pending items with a delivery date for the full catalog.
  • Priority-driven cataloging: focus on Critical and High priority items to support timely decisions.
  • Professional workflow guidance: provides a template for evidence, impact, effort, and category to maintain credibility under tight deadlines.

Quick Start

Run the cataloging workflow to generate a PARTIAL ANALYSIS technical debt catalog with explicit scope and a delivery date for the complete catalog.

Frequently Asked Questions about identifying-technical-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catalog technical debt quickly when facing tight deadlines?▼

Cataloging technical debt under time pressure requires prioritizing Critical and High priority items to deliver a structured partial catalog first, explicitly noting pending items and scheduling a delivery date for the full analysis.

What is the best way to prioritize technical debt items during an architecture assessment?▼

The best way to prioritize technical debt items is by focusing on Critical and High priority entries using a structured template that documents evidence, business impact, remediation effort, and category to support timely decisions.

Can I deliver a partial technical debt analysis instead of waiting for a complete audit?▼

Yes, you can deliver a partial technical debt catalog with explicit scope limitations, providing a set number of analyzed items while noting pending items and scheduling a delivery date for the full catalog.

What evidence should I include when documenting technical debt under time pressure?▼

When documenting technical debt under time pressure, include a structured template covering evidence, business impact, remediation effort, and category to maintain credibility while delivering a partial catalog.

Does technical debt cataloging require a full analysis before delivering actionable results?▼

No, technical debt cataloging does not require full analysis before delivery; it emphasizes execution discipline by providing an actionable partial catalog of prioritized items to support immediate decisions.

Related Skills

Explore More Software Engineering Skills→
tachyon-beeptachyon-beep
14

using-system-architect

Assess architecture quality and catalog technical debt from archaeologist outputs.

Community
Advanced
yknothingyknothing
1

tech-debt-management

Identify and manage technical debt as a structured registry with owners and timelines.

Community
Advanced
dapperdiversdapperdivers
1

financial-tracker

Calculate debt balances, interest accrual, budget variances, and payment deadlines from JSON state.

Community
Advanced
djankiesdjankies

template-based-generation-template

Generate structured content from templates with placeholder replacement and validation.

Community
Advanced