timmy-home/docs/weekly-triage-cadence.md

Weekly Backlog Triage Cadence

Issue: #685 - [OPS] timmy-home backlog reduced from 220 to 50 — triage cadence needed

Overview

This document describes the weekly triage cadence for maintaining the timmy-home backlog.

Problem

timmy-home had 220 open issues (highest in org). Through batch-pipeline codebase genome issues, the backlog was reduced to 50. To maintain this visibility, a weekly triage cadence is needed.

Current Status

• Total open issues: 50 (reduced from 220)
• Unassigned issues: 21
• Issues with no labels: 21
• Batch-pipeline issues: 19 (triaged with comments)

Solution

Weekly Triage Script (scripts/backlog_triage.py)

Script to analyze and report on the timmy-home backlog.

Features:

• Analyze open issues
• Identify stale issues
• Generate reports
• Create cron entries

Usage:

# Analyze backlog
python scripts/backlog_triage.py --analyze

# Generate report
python scripts/backlog_triage.py --report

# JSON output
python scripts/backlog_triage.py --json

# Generate cron entry
python scripts/backlog_triage.py --cron

Cron Entry

Add to crontab for weekly execution:

# Weekly timmy-home backlog triage
# Run every Monday at 9:00 AM
0 9 * * 1 cd /path/to/timmy-home && python3 scripts/backlog_triage.py --report > /var/log/timmy-home-triage-$(date +\%Y\%m\%d).log 2>&1

Triage Process

1. Run Weekly Analysis

# Generate report
python scripts/backlog_triage.py --report > triage-report-$(date +%Y%m%d).md

2. Review Stale Issues

• Issues >30 days old with no labels/assignee
• Close or re-prioritize as needed

3. Assign Labels and Owners

• Unassigned issues need owners
• Unlabeled issues need labels

4. Update Documentation

• Document triage cadence in CONTRIBUTING.md
• Add to morning report if applicable

Metrics to Track

Weekly Metrics

• Total open issues
• Unassigned issues
• Unlabeled issues
• Stale issues (>30 days)
• Batch-pipeline issues

Monthly Metrics

• Issue creation rate
• Issue closure rate
• Average time to close
• Label usage trends

Integration

With Morning Report

Add to morning report:

# In morning report script
python scripts/backlog_triage.py --report

With Cron

Add to system crontab:

# Edit crontab
crontab -e

# Add weekly triage
0 9 * * 1 cd /path/to/timmy-home && python3 scripts/backlog_triage.py --report > /var/log/timmy-home-triage-$(date +\%Y\%m\%d).log 2>&1

With CI/CD

Add to CI workflow:

- name: Weekly backlog triage
  run: |
    python scripts/backlog_triage.py --report > triage-report.md
    # Upload report as artifact or send notification

Related Issues

• Issue #685: This implementation
• Issue #1459: timmy-home backlog management
• Issue #1127: Perplexity Evening Pass triage (identified backlog)

Files

• scripts/backlog_triage.py - Weekly triage script
• docs/weekly-triage-cadence.md - This documentation

Conclusion

This implementation provides a weekly triage cadence to maintain the timmy-home backlog:

1. Weekly analysis of open issues
2. Reporting on stale and unassigned issues
3. Cron integration for automated execution
4. Metrics tracking for ongoing visibility

Use this script weekly to keep the backlog manageable.

License

Part of the Timmy Foundation project.