verify

/mz:verify

Verify that a phase achieved its GOAL by performing goal-backward verification against ROADMAP.md success criteria and PLAN.md must_haves. Spawns a verifier subagent via the Task tool that checks truths, artifacts (3-level), key links, and requirement coverage against the actual codebase. Produces VERIFICATION.md with results.

Note: This skill always works when invoked manually, regardless of the workflow.verifier config setting. The config toggle only controls whether /mz:go automatically suggests verification after execution.

Reference @skills/init/design-system.md for visual output formatting. Reference @skills/shared/presentation-standards.md for content formatting rules. Reference @skills/shared/terminology.md for official term definitions. Reference @skills/verify/verifier.md for verification protocol and spawning patterns.

Step 1: Display Banner

Output the stage banner:

+===============================================+
|  MEGAZORD > VERIFY                            |
+===============================================+

Step 2: Load Context and Validate

Read .planning/megazord.config.json. If missing, display error and stop:

## Error

Project not initialized — no megazord.config.json found.

`/mz:init`

If config exists, continue loading:

• Read .planning/STATE.md for current position.
• Read .planning/ROADMAP.md for phase details and success criteria.

Parse the user's message (text after /mz:verify) for arguments:

• {phase_num} -- verify a specific phase (optional, defaults to current)
• --partial -- verify even if some plans are incomplete (skip completion check)
• --milestone {version} -- run milestone audit mode instead of phase verification (see Step 3b)

Determine the plugin path for CLI commands:

1. Read plugin_path from the config JSON.
2. If plugin_path is not set in config, try ~/.claude/plugins/mz. Check if ~/.claude/plugins/mz/bin/megazord.mjs exists.
3. If neither exists, display error and stop: