tracking-technical-debt

What problem does it solve?

This Skill helps you capture and track technical debt when you cannot fix it immediately, ensuring issues are linked to concrete code markers so they don't get forgotten.

Core Features & Use Cases

• Bead creation: Create beads to capture the issue and assign labels (e.g., debt) for visibility.
• Code-marker linkage: Attach a marker to the relevant code location so the relationship is explicit.
• Two-path resolution: Decide to fix now (if quick) or track for later remediation; both options are logged.
• Batching tiny issues: Group multiple small issues under a single bead when they share context.

Quick Start

1. Create bead: bd create "O(n²) loop in auth validator needs optimization" --labels debt
2. Add code marker (in the relevant file): // DEBT[bd-xxxx]: O(n²) loop - should use Set for O(n) lookup That's it. Two steps, usually under 2 minutes.