bmad-loop-sweep

Triages deferred-work ledger entries into a machine-readable partition for the bmad-loop orchestrator.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-loop-sweep-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-loop-sweep
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-loop-sweep
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-loop-sweep-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deferred-work ledgers accumulate stale, already-fixed, or blocked entries whose recorded statuses are unreliable, making it impossible for an automated orchestrator to know what work can actually be scheduled. This Skill verifies every open entry against the real codebase and returns a deterministic, machine-readable triage plan. ## Core Features & Use Cases - Code-Verified Triage: Reads each open DW-<n> ledger entry, checks the referenced code and git history, and partitions entries into already_resolved, bundles, blocked, skip, or decisions with concrete evidence. - Bundle Planning: Groups buildable entries sharing a touchpoint into cohesive kebab-case-named bundles sized for a single dev session, with a 2-6 sentence intent per bundle. - Legacy Ledger Migration: In --migrate mode, rewrites freeform pre-DW-format ledgers into canonical ### DW-<n>: entries while preserving existing entries byte-identically and emitting a key-to-DW-id mapping. - Use Case: A bmad-loop sweep run spawns this Skill unattended; it reads deferred-work.md, verifies 12 open entries against the tree, and writes a validated result.json the orchestrator uses to close resolved entries and dispatch bundle dev sessions. ## Quick Start Invoke this skill inside a bmad-loop sweep session with BMAD_LOOP_MODE=1 set so it triages the deferred-work ledger and writes the result file.

Frequently Asked Questions about bmad-loop-sweep

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

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

Run this skill inside a bmad-loop sweep session with BMAD_LOOP_MODE=1. It reads deferred-work.md, verifies each open entry against the code and git log, and writes a result.json partitioning entries into already_resolved, bundles, blocked, skip, and decisions.

How does the sweep verify that a deferred entry is already resolved?

It reads the entry's location in the current tree, greps for the described symptom, and checks git log for commits touching the area since the entry's origin date. Only concrete evidence like a file:line or commit hash qualifies an entry as already_resolved.

Can this skill migrate an old freeform deferred-work file?

Yes, invoking it with --migrate and a manifest path triggers migration mode, which rewrites legacy bullets and strikethrough items into canonical DW entries. It is the only mode permitted to edit the ledger, and pre-existing DW entries must remain byte-identical.

Why does a sweep result.json fail validation?

Validation fails when open_ids do not exactly match the ledger's open entries, an id appears in zero or multiple categories, bundle names violate the kebab-case 40-character pattern, or required fields like evidence, blocker, or reason are empty.

When should a deferred entry become a decision instead of a bundle?

Entries touching frozen spec blocks, reversing human-approved scope decisions, changing API shapes with unbuilt consumers, or deferred as needing human judgment must be decisions with 2-4 options and a recommendation. When in doubt between bundle and decision, choose decision.