milestone-audit

Audit milestone deliverables against plan expectations using git history and tests.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill milestone-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-audit
Source: https://github.com/Tschonsen/spec-driven-claude-development/tree/main/plugin/sdcd/skills/milestone-audit
Command: npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill milestone-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestone-audit verifies that a milestone's deliverables align with the driving plan during implementation, ensuring code changes, tests, and brain files are in sync before proceeding.

Core Features & Use Cases

  • Verifies milestone completion by comparing implemented code, tests, and plan expectations.
  • Generates an audit trace by dispatching plan-drift-detector and sdcd-reviewer and recording results.
  • Updates design/AUDIT_LOG.md and CURRENT_STATE.md to reflect the outcome and next steps.

Quick Start

Run a milestone-audit for the active milestone to immediately generate an audit report and log.

Frequently Asked Questions about milestone-audit

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

FAQPage Schema
How do I audit code changes against a project plan before completing a milestone?

Milestone completion checks verify deliverables by comparing implemented code, tests, and brain files against the driving plan to ensure everything is in sync before proceeding.

What is plan drift detection in software engineering?

Plan drift detection compares actual implementation state against driving plan expectations to identify misalignments in code changes, tests, and brain files during milestone execution.

How do I generate an audit trace for a completed project milestone?

Generate an audit trace by dispatching plan-drift-detector and sdcd-reviewer to inventory actual state, then append results to AUDIT_LOG.md and update CURRENT_STATE.md with outcome and next steps.

Why do brain files and code changes go out of sync during milestone implementation?

Brain files and code changes desync when implementation drifts from the driving plan, requiring milestone audits to verify alignment of deliverables, tests, and brain-file hashes before proceeding.

Can I check git history and test status for milestone completion without external dependencies?

Yes, milestone audits run without external dependencies by checking git history, file changes, tests, and brain-file hashes internally to verify completion and update CURRENT_STATE.md.

What's the best way to verify milestone deliverables align with the driving plan?

The best way to verify milestone deliverables align with the driving plan is running end-to-end milestone audits that inventory actual state and dispatch plan-drift-detector to generate completion reports.