bmad-loop-sweep

Audit deferred-work ledger entries against codebase status and partition them.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-loop-sweep-marcmontecalvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-loop-sweep
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-loop-sweep
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-loop-sweep-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of stale and unorganized technical debt by automatically auditing, partitioning, and validating deferred work items against the actual state of the codebase.

Core Features & Use Cases

  • Automated Triage: Parses the deferred-work ledger and verifies each entry against current file locations and commit history to determine if issues are resolved, blocked, or ready for development.
  • Machine-Readable Partitioning: Categorizes work into bundles, decisions, or skips, ensuring the orchestrator has a clear, actionable plan for the next development cycle.
  • Legacy Migration: Safely converts freeform legacy ledgers into the canonical deferred-work format without manual intervention.

Quick Start

Run the bmad-loop-sweep skill to audit the current deferred-work ledger and generate a new triage plan.

Frequently Asked Questions about bmad-loop-sweep

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

FAQPage Schema
How do I automate triage for a deferred-work ledger?

Automated triage parses the deferred-work ledger and verifies each entry against current codebase file locations and commit history to determine if technical debt items are resolved, blocked, or ready for development.

What is the best way to audit stale technical debt against a codebase?

Auditing stale technical debt requires partitioning deferred-work entries by validating their status against the actual codebase, categorizing items into actionable bundles, decisions, or resolved skips for the next development cycle.

Can I convert freeform legacy technical debt ledgers into a structured format?

Legacy migration safely converts freeform legacy ledgers into the canonical deferred-work format without manual intervention, requiring strict adherence to the deferred-work-format and automation-mode schemas for deterministic output.

Do I need a specific orchestrator environment to partition technical debt tasks?

Task partitioning operates within a bmad-loop orchestrator environment to categorize deferred work into bundles, decisions, or resolved items, ensuring the orchestrator receives a clear, machine-readable plan for the next cycle.

Why does automated codebase triage require strict schema adherence?

Strict adherence to the deferred-work-format and automation-mode schemas is required because the triage automation relies on deterministic output to accurately verify ledger entries against current file locations and commit history.