phase-closure-audit

To audit a project phase for closure readiness, you need to verify milestones, ADRs, and closure criteria. The audit retrieves phase milestones, confirms referenced ADRs are accepted, and evaluates closure conditions to generate a structured readiness report.

Phase closure readiness is the validation that all milestone conditions and documentation are complete before a release. ADR verification confirms that every referenced Architecture Decision Record exists, is accepted, and conforms to the codebase via sub-agent checks.

You generate a closure audit report by evaluating the GitHub milestone description and its closure criteria. The audit categorizes each condition as MET, NOT MET, or UNVERIFIABLE, outputting the results to a markdown file in the docs/maintainer directory.

Yes, GitHub CLI access is required to retrieve phase milestones and parse their descriptions. The repository must also contain a docs/adr directory structure to enable sub-agent verification of Architecture Decision Record conformance.

When a closure criteria condition is unverifiable during a phase audit, it is explicitly categorized as UNVERIFIABLE. The generated closure audit report will flag these conditions, alongside MET and NOT MET items, to indicate manual verification needs and blockers.

Yes, a phase audit prevents premature releases by ensuring phase documentation and ADR compliance meet defined standards. It systematically checks milestone descriptions and closure criteria, blocking closure until all architectural and code evidence is verified.