design-debt-tracker

Maintain a design debt register in design-state.md with status workflows.

234|55|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designpowers --skill design-debt-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-debt-tracker
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debt-tracker
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill design-debt-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a living register of design debt, capturing conscious compromises and deferred findings so they are visible across iterations.

Core Features & Use Cases

  • Create and maintain a Design Debt Register in design-state.md to track items by ID, date, source, severity, and status.
  • Support escalation and resolution workflows—Open, Resolved, Accepted, Escalated.
  • Provide planning input by surfacing top debt candidates for each cycle.

Quick Start

Use the design-debt-tracker to capture the first debt item after critique by adding an entry to the Design Debt Register in design-state.md.

Frequently Asked Questions about design-debt-tracker

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

FAQPage Schema
How do I track design debt across project iterations?

Track design debt by maintaining a living register in design-state.md that captures deferred findings and conscious compromises by ID, date, source, severity, and status across iterations. This keeps compromises visible and actionable during planning.

What is a design debt register and when do I need it?

A design debt register is a living record of deferred design findings and conscious compromises. You need it after critiques or accessibility reviews to ensure visibility across iterations and prevent deferred items from being forgotten.

How do I manage design debt workflow statuses like escalation and resolution?

Manage design debt workflows using four statuses: Open, Resolved, Accepted, and Escalated. This structure supports capture, review, escalation, and resolution processes directly within the design-state.md register format.

Can I surface top design debt candidates for iteration planning?

Yes, the design debt tracker provides planning input by surfacing top debt candidates for each cycle. It applies before planning to identify the most critical deferred findings and decisions from the register.

Does the design debt tracker work without external dependencies?

Yes, the design debt tracker operates without external dependencies. It solely relies on enforcing the register format within design-state.md to track and maintain items across project iterations.

What is the best way to capture design compromises after a design review?

The best way to capture design compromises is adding an entry to the Design Debt Register in design-state.md immediately after critique. This logs the item with its source, severity, and status for future resolution.