beads-audit

Run beads graph health checks using bd status and bd doctor to identify orphaned issues, circular dependencies, and misconfigurations, providing clear remediation guidance and runbook instructions for routine maintenance.

Automate beads issue graph maintenance by performing periodic health checks during weekly cycles or after major graph changes, using bd lint and bd dep cycles to detect stale issues and surface structural fixes before planning sessions.

Run beads lint and graph health checks during weekly maintenance cycles, after major graph changes, or before planning sessions to detect disorganized structures that risk affecting project planning and issue tracking integrity.

The beads audit process works standalone without additional dependencies or components, relying solely on Beads toolkit commands like bd status, bd doctor, bd lint, and bd dep cycles to assess graph health and surface fixes.

Fix circular dependencies in the beads issue graph by running bd dep cycles to detect them, then following the runbook-style remediation guidance provided by the health check output to resolve structural misconfigurations and restore graph integrity.

Beads graph health maintenance matters before planning sessions because disorganized structures, orphaned issues, and circular dependencies directly affect planning accuracy, and running bd doctor and bd lint surfaces these integrity issues early to prevent downstream problems.