claude-tweaks:tidy

To audit and sanitize a project backlog, trigger a tidy scan across INBOX, DEFERRED, specs, design docs, and plans. This surfaces stale items and produces a single consolidated report with recommended grooming steps and ownership for actionable maintenance.

Backlog grooming is the structured triage and validation of project artifacts to maintain a healthy specification system. You need it when stale items accumulate in your INBOX or DEFERRED folders, requiring safe actions to align specs and plans for focused work.

You can surface stale items by running a tidy audit that scans DEFERRED entries, design docs, and execution plans. It enforces structured triage with validation and consolidates findings into a single tidy report with recommended next steps.

Yes, tidy audits apply across related git worktrees to surface actionable grooming steps during routine maintenance. It validates backlog entries and promotes safe triage actions to maintain clean specification handoffs across your project branches.

The best way to consolidate backlog findings is to trigger a tidy audit that scans all project artifacts. It produces a single consolidated tidy report featuring recommended next steps, ownership details, and safe validation handoffs.

Your project backlog needs structured triage and validation to ensure clean handoffs to the specify, build, and review flow. Tidy enforces safe actions during grooming, preventing stale or misaligned specs from disrupting downstream execution.