gsd-audit-milestone

Audit milestone completion against original intent before archiving.

Updated Apr 2, 2026

Search Tags:#workflow #integration #verification #audit #milestones #archiving #cross-phase

Ready to run

npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-audit-milestone-ev3rlit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-audit-milestone
Source: https://github.com/ev3rlit/magam-canonical-archive/tree/main/.codex/skills/gsd-audit-milestone
Command: npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-audit-milestone-ev3rlit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit milestone completion against original intent to ensure alignment before archiving.

Core Features & Use Cases

Cross-check milestone definitions against initial objectives.
Aggregate verification artifacts and surface gaps for remediation.
Orchestrate a lightweight cross-phase integration check to ensure readiness for archival.

Quick Start

Run the audit-milestone workflow to compare milestones against the original intent and generate a verification report.

Frequently Asked Questions about gsd-audit-milestone

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

FAQPage Schema

How do I verify milestone completion against original project objectives before archiving?▼

You can verify milestone completion by running a cross-phase audit that checks alignment between original intent and predefined milestones. This process reviews verification artifacts to ensure all objectives are met before project archival.

What is cross-phase verification in project workflow audits?▼

Cross-phase verification is an audit mechanism that validates milestone completion across different project stages. It aggregates tech debt and gaps by cross-checking verification artifacts against initial objectives to ensure readiness for archiving.

How do I aggregate tech debt and gaps before archiving a project milestone?▼

You aggregate tech debt and gaps by orchestrating an integration checker during the milestone audit. This workflow compares your summary artifacts against predefined milestones to surface any outstanding issues requiring remediation.

Do I need a VERIFICATION.md file to run a milestone audit?▼

Yes, a VERIFICATION.md file is required for the milestone audit. The audit workflow applies to project environments where VERIFICATION.md and summary artifacts must align with predefined milestones across phases before archiving.

Can I use this workflow to check if my summary artifacts align with predefined milestones?▼

Yes, you can use this workflow to cross-check your summary artifacts against predefined milestones. It enforces cross-phase verification to ensure your artifacts align with the original intent before proceeding to archival.

When should I not use an automated audit workflow for project archiving?▼

You should avoid using an automated audit workflow for archiving if your project lacks predefined milestones or VERIFICATION.md artifacts. The process requires structured verification documentation to properly aggregate gaps and run cross-phase integration checks.