From Ferrox Core
Audit milestone completion against original intent before archiving
How this skill is triggered — by the user, by Claude, or both
Slash command
/ferrox-core:ferrox-audit-milestone [version][version]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
This command IS the orchestrator. Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
<execution_context> @~/.claude/ferrox-core/workflows/audit-milestone.md </execution_context>
Version: $ARGUMENTS (optional — defaults to current milestone)Core planning files are resolved in-workflow (init milestone-op) and loaded only as needed.
Completed Work: Glob: .planning/phases//-SUMMARY.md Glob: .planning/phases//-VERIFICATION.md
Execute end-to-end. Preserve all workflow gates (scope determination, verification reading, integration check, requirements coverage, routing).npx claudepluginhub ferroxlabs/ferrox-factory --plugin ferrox-coreCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.