with one click
maestro-milestone-audit
// Audit current milestone for cross-phase integration gaps
// Audit current milestone for cross-phase integration gaps
| name | maestro-milestone-audit |
| description | Audit current milestone for cross-phase integration gaps |
| argument-hint | ["<milestone>"] |
| allowed-tools | ["ask_question","define_subagent","grep_search","invoke_subagent","manage_subagents","run_command","send_message","view_file","write_to_file"] |
Data source: state.json.artifacts[] filtered by current milestone.
Produces audit report at .workflow/milestones/{milestone}/audit-report.md.
Pipeline position: downstream of maestro-verify (all phases verified), upstream of maestro-milestone-complete.
<required_reading> @~/.maestro/workflows/milestone-audit.md </required_reading>
Milestone: $ARGUMENTS (optional -- defaults to current_milestone from state.json).Requires: All phases in the milestone should have completed execute artifacts.
Data source:
.workflow/state.json — artifacts[], current_milestone, milestones[].workflow/roadmap.md — milestone-to-phase mapping (standard milestones only)Adhoc milestone support (D-008): When the target milestone has type == "adhoc" (or type field is missing, defaulting to "standard"), the audit skips roadmap.md parsing and phase coverage checks. It only validates artifact chain completeness (PLN→EXC exists) and runs integration checks.
.workflow/codebase/doc-index.json exists → Read ARCHITECTURE.md for integration checksmaestro spec load --category review — load review standards for auditmaestro wiki list --category reviewmaestro wiki load <id1> [id2...]
Audit checklist steps (phase coverage, ad-hoc completeness, execution completeness, cross-artifact integration) are defined in workflow milestone-audit.md.
=== MILESTONE AUDIT READY ===
Milestone: {milestone}
Verdict: {PASS|FAIL}
Phases audited: {N}
Integration gaps: {N}
Report: .workflow/milestones/{milestone}/audit-report.md
End the step by calling the CLI (no text block output):
maestro ralph complete <idx> --status {STATUS} [--evidence .workflow/milestones/{milestone}/audit-report.md]
Status verdicts:
--concerns--reason| Condition | Suggestion |
|---|---|
| Verdict PASS | /maestro-milestone-complete {milestone} |
| Verdict FAIL, integration gaps | /maestro-plan --gaps |
| Verdict FAIL, incomplete execution | /maestro-execute |
<error_codes>
| Code | Severity | Condition | Recovery |
|---|---|---|---|
| E001 | error | Milestone identifier required | Check arguments format |
| E002 | error | Milestone not found in state.json | Check milestone ID |
| E003 | error | No execute artifacts found for milestone | Run maestro-execute first |
| W001 | warning | Some phases lack complete artifact chains | Review incomplete phases |
| </error_codes> |
<success_criteria>
Use when a topic needs structured multi-dimensional investigation before planning or decision-making
Generate formal specification package (Product Brief, PRD, Architecture, Epics) through 6-phase document chain
Use when exploring ideas, evaluating approaches, or needing multi-perspective analysis before implementation
Use when a confirmed plan is ready for implementation
Use when stress-testing a plan, idea, or requirement against codebase reality before brainstorming
Initialize project with auto state detection