tech-debt-capture

Extract Phase 4 technical debt from evaluation reports into Atomic Tickets.

1|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/tarrragon/claude --skill tech-debt-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-capture
Source: https://github.com/tarrragon/claude/tree/main/skills/tech-debt-capture
Command: npx skills add https://github.com/tarrragon/claude --skill tech-debt-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

This Skill automates extracting Phase 4 technical debt from evaluation reports and converts them into Atomic Tickets to streamline remediation.

Core Features & Use Cases

  • Automated TD extraction: Parses Phase 4 work logs and identifies debt items with ID, description, risk level, and suggested timing.
  • UC-driven version mapping: Applies UC-Oriented rules to map debts to target versions, with optional manual override.
  • Ticket generation & tracking: Creates Atomic Tickets with Frontmatter v3.0 and updates the todolist for progress visibility.
  • Use Case: After Phase 4 evaluation, converts each debt item into a concrete ticket and updates the tracking board automatically.

Quick Start

Use the tech-debt-capture skill to parse a Phase 4 evaluation log and generate tickets for the v0.20.0 release.

Frequently Asked Questions about tech-debt-capture

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

FAQPage Schema
How do I extract tech debt items from evaluation reports and convert them to tickets?

Tech debt extraction works by parsing Phase 4 evaluation logs to identify debt items with ID, risk level, and timing, then generating Atomic Tickets. This automation streamlines remediation by converting raw evaluation data into structured, actionable work tickets.

Can I override version mapping for tech debt tickets to target a specific release?

Yes, version mapping supports manual override to target specific releases. While UC-Oriented rules automatically map debts to target versions, you can optionally specify a manual override like v0.20.0 to direct tickets to your desired release.

What is an Atomic Ticket and how does it track tech debt remediation progress?

An Atomic Ticket is a structured work item generated with Frontmatter v3.0 metadata that represents a single tech debt remediation task. It automatically updates the todolist upon creation, providing continuous progress visibility for tracked debt items.

Does tech debt ticket generation require any specific dependencies?

Tech debt ticket generation requires the pyyaml dependency for parsing and processing configuration. This lightweight Python library handles the YAML structures used in Frontmatter v3.0 ticket generation and evaluation log parsing.

What's the best way to automate Phase 4 tech debt tracking after evaluation?

Automating Phase 4 tech debt tracking is best handled by parsing evaluation reports to extract debt items and generating Atomic Tickets with automatic todolist updates. This eliminates manual ticket creation and ensures every identified debt item is tracked.