beads-workflow

Fix a list of issues one-by-one, each with its own beads task, commit, and push

Work on an epic from beads until completion, then create a PR

Autonomously sweep and triage ALL open beads (bd tasks) the way a careful engineer would by hand — reconcile each bead against reality (git history, passing tests, tool versions, whether its blockers have since closed), CLOSE the ones already satisfied with cited evidence, PARK the ones blocked on an external resource with a ready-to-run playbook, and SURFACE genuine JT-only decisions into an end-of-run report instead of guessing. Use this whenever the user wants to triage beads, clean up stale issues, sweep or prune open beads, audit the backlog, close out finished-but-still-open tasks, or asks why so many beads are piling up — and it is safe to run repeatedly and unattended (e.g. from a scheduled agent). Also fires on "triage the backlog", "clear out stale beads", "which of these beads are already done", and "auto-triage".

Match a change-set against the tripwire anchors that parked beads (bd issues) declare, and surface each parked bead whose watched code you're about to change — the edit-time warning that `bd ready` can't give, because it only fires when someone asks for work, never when you touch the file a bead warns about. Use when reviewing or creating a PR, before finishing a change, or when asked to "check tripwires", "scan for tripwires", or "what parked beads touch this change". A parked bead plants a `tripwire-paths:` line naming where its knowledge bites; this scans your diff against those anchors and reports each hit as bead-id → matched file → the bead's one-line why. Safe and read-only.