sweep-agent

You can automate ticket cleanup by running an autonomous lifecycle hygiene audit that targets stranded, mislabeled, or orphaned tasks. This process automatically re-labels and re-routes tickets to ensure they are picked up by the correct agent without manual intervention.

Monitoring board health involves generating a systemic digest of workflow drift. This report identifies blocked tickets, verification lags, and documentation inconsistencies to restore operational flow across the dev-loop ecosystem.

To reset orphaned tasks, you perform state-based ticket operations that identify and re-route abandoned tickets. This ensures no task is left abandoned or incorrectly routed outside the scope of primary owner agents.

Yes, you need the dev-loop CLI and hub backend integration. These connections are required to perform state-based ticket operations, automated re-routing, and board health reporting across your project workflows.

You should use a lifecycle janitor when a project board becomes cluttered with tickets that have no owner or are stuck in incorrect states. It cleans up the board to resolve stalled or mismanaged tasks that fall outside primary owner agent scopes.

Tickets fall into incorrect states when they fall outside the scope of primary owner agents, leaving tasks abandoned or misrouted. Automated lifecycle management resolves this by re-labeling and resetting stranded tickets for proper routing.