master-plan-auditor

Name: master-plan-auditor
Availability: InStock
Author: endlessblink

Audit task status consistency across MASTER_PLAN.md, beads, and git history.

Updated Nov 29, 2025

Search Tags:#workflow #audit #beads #reporting #task-status #master_plan

Ready to run

npx skills add https://github.com/endlessblink/flow-state --skill master-plan-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: master-plan-auditor
Source: https://github.com/endlessblink/flow-state/tree/main/.claude/skills/master-plan-auditor
Command: npx skills add https://github.com/endlessblink/flow-state --skill master-plan-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and validate the consistency of task statuses across MASTER_PLAN.md locations, beads, and git history to prevent drift and miscommunication.

Core Features & Use Cases

Ingests statuses from table, subtasks, and headers in MASTER_PLAN.md.
Cross-references with beads and git activity to surface stale tasks and mismatches.
Generates evidence-backed recommendations (without auto-marking) for human verification.

Quick Start

Run the audit command to scan MASTER_PLAN.md for status consistency and generate a recommended report for review.

Frequently Asked Questions about master-plan-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit task statuses in MASTER_PLAN.md for consistency across git history and beads?▼

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.

Why do task statuses drift between my MASTER_PLAN.md, beads, and code history?▼

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.

Can I automatically mark task statuses as complete based on git history and beads?▼

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.

What is the best way to surface stale tasks tracked in a MASTER_PLAN.md file?▼

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.

Does the MASTER_PLAN.md audit work with projects tracking progress through beads issues and code history?▼

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.

What limitations exist when validating status mismatches across MASTER_PLAN.md locations?▼

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.