master-plan-auditor

You can audit task statuses by parsing all MASTER_PLAN.md sections, normalizing statuses, and correlating evidence from beads and git commits to surface stale tasks and mismatches. The audit generates a structured report with evidence-backed recommendations.

Status drift occurs when task updates in MASTER_PLAN.md headers or subtasks are not reflected in beads or git activity. The audit workflow detects this by cross-referencing task IDs, bead states, and commit history to identify inconsistencies.

No, the audit does not auto-mark any task statuses. It produces evidence-backed recommendations for human verification, ensuring you manually validate stale tasks and status mismatches before updating your tracking system.

The best way to surface stale tasks is to run an audit that ingests statuses from table, subtasks, and headers in MASTER_PLAN.md, then cross-references them with beads and git activity to generate a structured report for review.

Yes, the audit specifically applies to projects that track progress using MASTER_PLAN.md, beads issues, and code history. It correlates commits, bead states, and task IDs to validate status consistency and prevent miscommunication.

A key limitation is that the audit does not auto-mark or modify any task statuses. It only parses sections, normalizes data, and produces recommendations, requiring human verification before any tracking updates are made.