bmad-loop-sweep

Automated triage for a deferred-work ledger validates open entries against current codebase and git history to categorize tasks as resolved, actionable, blocked, or decision-required. It uses deterministic validation to ensure ledger integrity.

Auditing stale technical debt entries involves checking code, git history, and file references to determine if issues are still relevant. This process partitions entries into resolved, actionable bundles, or human-decision requirements.

Migrating a legacy technical debt ledger safely converts older, freeform deferred-work entries into a standardized canonical format required for modern orchestration. This ensures compatibility with automated sweep workflows.

Automated codebase verification for deferred-work triage checks code, file references, and git history to validate open issues. It operates within automated sweep workflows to generate a machine-readable triage plan.

Partitioning technical debt tasks requires invoking an automated sweep within an active session to audit the deferred-work ledger. This generates a machine-readable triage plan categorizing resolved, blocked, and actionable items.

Automated sweeps for technical debt triage should not be used when entries require subjective human analysis or lack sufficient git history and file references for deterministic validation. Such items are categorized as decision-required.