tech-debt-triage

To consolidate technical debt, scan `technical-debt.md` files across your monorepo, group related cross-service issues based on defined heuristics, and generate parent/sub-task issues. This transforms scattered notes into clear, actionable tasks ready for development.

Yes, you can create Linear issues from `technical-debt.md` files. The process scans the documentation, classifies severity, requires user approval before creation, and generates detailed parent and sub-task issues directly in your backlog.

The best way to triage cross-service technical debt is to consolidate related problems intelligently, such as grouping missing logging across multiple services into a single manageable Linear issue, streamlining backlog management and triage.

Yes, the issue creation process requires user approval before generating tasks. After scanning files and consolidating cross-service technical debt, it presents a summary for triage, ensuring you review and approve all parent and sub-task issues before they are created.

Severity classification works by evaluating consolidated cross-service issues during the scan of `technical-debt.md` files. It categorizes the technical debt, includes the severity in the generated summary, and applies it to the parent and sub-task issues before user approval.

A limitation when scanning `technical-debt.md` files is that consolidation relies on defined heuristics to group cross-service issues. If documentation is missing or poorly structured, the automated severity classification and parent/sub-task issue generation may not capture the full context.