bmad-loop-sweep

Triages deferred-work ledger entries into machine-readable bundles, resolutions, and decisions.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-loop-sweep-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-loop-sweep
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-loop-sweep
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-loop-sweep-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deferred-work ledgers accumulate stale, unreliable entries that no one verifies against the actual codebase, leaving orchestrators unable to decide what to build, close, or escalate. This Skill verifies every open entry against the code and returns a validated, machine-readable triage partition. ## Core Features & Use Cases - Code-Verified Triage: Checks each open DW entry against the current tree, git history, and file:line evidence before classifying it as already_resolved, bundle, blocked, skip, or decision. - Bundle Planning: Groups buildable entries sharing a touchpoint into cohesive, kebab-case-named bundles sized for a single dev session, with 2-6 sentence intents. - Legacy Ledger Migration: Rewrites freeform pre-DW-format deferred-work files into canonical entries when invoked with --migrate, preserving existing entries byte-identically. - Use Case: During a bmad-loop sweep run, the orchestrator spawns this Skill to drain a deferred-work.md ledger; it returns a result.json the orchestrator validates field-by-field and executes deterministically. ## Quick Start Invoke this Skill inside a bmad-loop sweep session with BMAD_LOOP_MODE=1 to triage the project's deferred-work ledger into a validated result.json.

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 set. It reads deferred-work.md, verifies each open entry against the code, and writes a result.json partitioning entries into bundles, already_resolved, blocked, skip, and decisions.

How does the sweep verify whether a deferred item is already fixed?

It reads the entry's location in the current tree, greps for the 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 legacy deferred-work files to the DW format?

Yes, invoking it with --migrate and a manifest path triggers migration mode, which rewrites freeform legacy items into canonical DW entries. Pre-existing entries stay byte-identical, and the orchestrator validates the result against the manifest's done flags.

When does a deferred item become a human decision instead of a bundle?

Frozen-block renegotiations, reversals of human-approved scope decisions, and API-shape changes affecting unbuilt consumers are always decisions. Each decision gets 2-4 concrete options with effects and a recommendation.

Why does a sweep result fail validation?

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

Can I run this Skill manually outside bmad-loop?

No, it is automation-only and checks the BMAD_LOOP_MODE environment variable on activation. If the variable is not set to 1, it states that it only runs inside a bmad-loop sweep and ends its turn.