ferrox-audit-milestone

Verify completed milestones against their original definition of done.

21|9|Updated Jul 21, 2026

Search Tags:#software delivery #tech debt #requirements coverage #end-to-end validation #integration review #milestone verification

Ready to run

npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-audit-milestone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ferrox-audit-milestone
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-audit-milestone
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-audit-milestone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when a milestone appears complete but needs a rigorous check against the original requirements, phase outputs, and integration expectations before it can be trusted.

Core Features & Use Cases

Milestone Verification: Confirms that completed work matches the definition of done and the intended scope.
Cross-Phase Integration Review: Checks wiring between phases, deferred gaps, and tech debt that may affect the final result.
End-to-End Validation: Suitable for reviewing shipped work, release candidates, or any milestone that needs a final orchestration pass before approval.

Quick Start

Use the ferrox-audit-milestone skill to verify the current milestone against its original requirements and report any gaps.

Frequently Asked Questions about ferrox-audit-milestone

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

FAQPage Schema

How do I verify a completed software milestone against its original requirements?▼

Milestone verification confirms that completed work matches the original definition of done and intended scope by reading existing verification artifacts, aggregating deferred gaps, and checking requirements coverage before approval.

What is cross-phase integration review in software delivery?▼

Cross-phase integration review checks the wiring between delivery phases, identifies deferred gaps, and aggregates tech debt status to ensure integration expectations are met before a milestone ships.

How do I perform end-to-end validation before approving a release candidate?▼

End-to-end validation applies a final orchestration pass to review shipped work and release candidates, ensuring cross-phase integration and requirements coverage are satisfied without bypassing workflow gates.

Can I use milestone verification to track deferred gaps and tech debt?▼

Yes, milestone verification aggregates deferred gaps and tech debt status from existing artifacts to report whether they affect the final result before shipping approval.

Does milestone verification bypass workflow gates during phased software delivery?▼

No, milestone verification explicitly requires reading existing verification artifacts and aggregating integration status without bypassing workflow gates during phased software delivery.

When do I need end-to-end validation for a software delivery milestone?▼

End-to-end validation is needed when a milestone appears complete but requires a rigorous check against original requirements, phase outputs, and integration expectations before it can be trusted and shipped.