gpd-audit-milestone

To audit milestone completion, you need to validate phase verifications against ROADMAP, REQUIREMENTS, STATE, and SUMMARY artifacts. This process detects gaps, open questions, and deferred analyses to ensure research alignment and readiness.

Cross-phase consistency checking assesses research coherence by evaluating notation stability, parameter usage, and narrative integrity across completed phases. It coordinates checks against ROADMAP and REQUIREMENTS to collect phase-level gaps.

Generating a milestone audit report involves aggregating VERIFICATION.md and STATE.md files across phases to produce a structured .gpd/v{version}-MILESTONE-AUDIT.md file. This report contains a YAML header and full markdown findings for publication readiness.

Yes, you can spawn a consistency-checking subagent to evaluate cross-phase coherence, notation stability, and parameter usage. This subagent works by aggregating ROADMAP.md and REQUIREMENTS.md to verify scope and readiness.

You need to verify milestone scope and readiness when completing research phases to ensure alignment with original goals. This involves aggregating ROADMAP.md, REQUIREMENTS.md, STATE.md, and VERIFICATION.md to detect deferred analyses and open questions.

The limitation of aggregating STATE.md and VERIFICATION.md is that it relies on the completeness of these artifacts to detect gaps and open questions. Without accurate phase-level documentation, the consistency checker cannot fully assess cross-phase coherence and narrative integrity.