map

/mz:map

Analyze an existing codebase by spawning parallel mapper agents that produce structured analysis documents. Enables brownfield project onboarding by understanding architecture, tech stack, code quality, and concerns.

Reference @skills/init/design-system.md for visual output formatting. Reference @skills/map/mapper.md for agent spawning patterns.

Step 1: Display Banner

Output the stage banner:

╔═══════════════════════════════════════════════╗
║  ⚡ MEGAZORD ► MAP                            ║
╚═══════════════════════════════════════════════╝

Step 2: Load Context

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

╔═══════════════════════════════════════════════╗
║  ✗ Project Not Initialized                    ║
╠═══════════════════════════════════════════════╣
║  No megazord.config.json found.               ║
║  Run /mz:init to set up your project first.   ║
╚═══════════════════════════════════════════════╝

If config exists, continue loading:

• Read .planning/megazord.config.json for project settings.

Determine the plugin path:

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:

   Plugin path not configured. Run /mz:settings and set plugin_path, or re-run /mz:init.

Parse the user's message for arguments:

• Optional focus parameter: /mz:map architecture, /mz:map tech, etc.
• Map focus aliases to canonical names:
  • arch -> architecture
  • conventions -> quality
• Valid focus values: tech, architecture, quality, concerns
• Default (no argument): run all 4 areas

Display the target:

▸ Target
  {focus area name, or "All areas" if no focus specified}

Step 3: Check Existing Map

Check if .planning/codebase/ directory exists and contains analysis documents.

Use Bash to check: ls .planning/codebase/*.md 2>/dev/null | wc -l