中文
devexamples
← Workflows

阅读中文版本

Tech Debt Triage

Improve team process: triage tech debt, review pull-request staleness, and confirm retrospective actions are tracked to closure.

intermediate~30 minteamprocessquality

Objective

Keep tech debt bounded and ensure no pull request or retrospective action stalls without an owner.

Environment

  • A working team environment with access to the target system and its tooling
  • Configuration and credentials for the team workflow installed and verified
  • A rollback or undo path documented before any change is applied

Steps

1. Triage tech debt

List open tech-debt issues by age and impact and assign an owner and a target quarter to the top items.

Expected state: Every top tech-debt item has an owner and a target.

2. Review stale pull requests

Find pull requests open longer than the threshold and ping the author or reassign to keep them moving.

Expected state: No pull request is open beyond the threshold without a recent comment.

3. Track retrospective actions

Export actions from recent retrospectives and confirm each has an owner, a due date, and a status.

Expected state: Every retrospective action is tracked and none is orphaned.

Decision points

How should tech debt be prioritized?

  • By impact and age together
  • By age alone to be fair

Prioritize by impact first; old low-impact debt can wait while high-impact debt compounds.

Expected outcome

Keep tech debt bounded and ensure no pull request or retrospective action stalls without an owner. The change is verified and a rollback path is confirmed.

Verification

Keep tech debt bounded and ensure no pull request or retrospective action stalls without an owner. Compare before and after metrics and confirm the expected state is reached.

Cleanup

Archive the run artifacts, remove temporary credentials, and update the runbook with any changes.

Overview

Improve team process: triage tech debt, review pull-request staleness, and confirm retrospective actions are tracked to closure. The goal is to keep tech debt bounded and ensure no pull request or retrospective action stalls without an owner.

gh pr list --state open --search "created:<2026-09-25" --json number,title,author

Steps

  1. Triage tech debt. List open tech-debt issues by age and impact and assign an owner and a target quarter to the top items. Expected: Every top tech-debt item has an owner and a target.

  2. Review stale pull requests. Find pull requests open longer than the threshold and ping the author or reassign to keep them moving. Expected: No pull request is open beyond the threshold without a recent comment.

  3. Track retrospective actions. Export actions from recent retrospectives and confirm each has an owner, a due date, and a status. Expected: Every retrospective action is tracked and none is orphaned.

Verification

Confirm the outcome by checking: keep tech debt bounded and ensure no pull request or retrospective action stalls without an owner. Run the verification command and compare the result against the expected state. If any check fails, stop and investigate before continuing.

Decision points

  • How should tech debt be prioritized?
    • By impact and age together
    • By age alone to be fair
    • Recommendation: Prioritize by impact first; old low-impact debt can wait while high-impact debt compounds.