/mikado
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking
> /plugin marketplace add nWave-ai/nWave > /plugin install nw@nwave-marketplace
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/mikado
Context preview
What this command does when you run it.
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking
Command definition
mikado.mddescription: "[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking"
argument-hint: "[refactoring-goal] - Optional: --complexity=[simple|moderate|complex] --visualization=[tree|graph]"
NW-MIKADO: Complex Refactoring with Mikado Method
> **EXPERIMENTAL**: Under active development. Behavior and output format may change between versions.
**Wave**: CROSS_WAVE **Agent**: Crafty (nw-software-crafter) **Command**: `*mikado`
Overview
Plan and execute complex refactoring using the Mikado Method. Builds dependency {visualization} through iterative exploration|tracks discoveries via commits|executes leaf-to-goal bottom-up. For architectural changes spanning multiple classes where simple refactoring is insufficient.
Context Files Required
- src/\* - Codebase to refactor
- docs/product/architecture/brief.md - Target architecture (if available)
Agent Invocation
@nw-software-crafter
Execute \*mikado for {refactoring-goal}.
**Context Files:**
- src/\*
- docs/product/architecture/brief.md
**Configuration:**
- refactoring_goal: "{goal description with business value}"
- complexity: complex # simple/moderate/complex
- visualization: {tree|graph} # tree = indented markdown checklist, graph = Mermaid dependency diagram
Progress Tracking
The invoked agent MUST create a task list from its workflow phases at the start of execution using TaskCreate. Each phase becomes a task with the gate condition as completion criterion. Mark tasks in_progress when starting each phase and completed when the gate passes. This gives the user real-time visibility into progress.
Success Criteria
- [ ] Mikado {visualization} persisted at docs/mikado/{goal-name}.mikado.md
- [ ] Discovery commits capture each exploration attempt
- [ ] All leaf nodes implemented bottom-up
- [ ] Goal node achieved with all tests passing
- [ ] {visualization_label} stable (no new dependencies emerging)
**Visualization labels**: tree → "Tree", graph → "Graph". Use the selected visualization type in all output messages (e.g., "Wrote the Mikado tree" or "Wrote the Mikado graph").
Next Wave
**Handoff To**: {invoking-agent-returns-to-workflow} **Deliverables**: Refactored codebase + Mikado {visualization} documentation
Examples
Example 1: Extract shared domain model
/nw-mikado "Extract shared domain model from monolithic service layer"
Crafty builds Mikado dependency {visualization} through iterative exploration, discovers 12 leaf nodes across 4 modules, executes bottom-up from leaves to goal with discovery commits at each step.
Expected Outputs
docs/mikado/{goal-name}.mikado.md
src/* (refactored implementation)
Discovery-tracking commits in git logRead more
description: "[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking" argument-hint: "[refactoring-goal] - Optional: --complexity=[simple|moderate|complex] --visualization=[tree|graph]"
NW-MIKADO: Complex Refactoring with Mikado Method
> **EXPERIMENTAL**: Under active development. Behavior and output format may change between versions.
**Wave**: CROSS_WAVE **Agent**: Crafty (nw-software-crafter) **Command**: `*mikado`
Overview
Plan and execute complex refactoring using the Mikado Method. Builds dependency {visualization} through iterative exploration|tracks discoveries via commits|executes leaf-to-goal bottom-up. For architectural changes spanning multiple classes where simple refactoring is insufficient.
Context Files Required
- src/\* - Codebase to refactor
- docs/product/architecture/brief.md - Target architecture (if available)
Agent Invocation
@nw-software-crafter
Execute \*mikado for {refactoring-goal}.
**Context Files:**
- src/\*
- docs/product/architecture/brief.md
**Configuration:**
- refactoring_goal: "{goal description with business value}"
- complexity: complex # simple/moderate/complex
- visualization: {tree|graph} # tree = indented markdown checklist, graph = Mermaid dependency diagram
Progress Tracking
The invoked agent MUST create a task list from its workflow phases at the start of execution using TaskCreate. Each phase becomes a task with the gate condition as completion criterion. Mark tasks in_progress when starting each phase and completed when the gate passes. This gives the user real-time visibility into progress.
Success Criteria
- [ ] Mikado {visualization} persisted at docs/mikado/{goal-name}.mikado.md
- [ ] Discovery commits capture each exploration attempt
- [ ] All leaf nodes implemented bottom-up
- [ ] Goal node achieved with all tests passing
- [ ] {visualization_label} stable (no new dependencies emerging)
**Visualization labels**: tree → "Tree", graph → "Graph". Use the selected visualization type in all output messages (e.g., "Wrote the Mikado tree" or "Wrote the Mikado graph").
Next Wave
**Handoff To**: {invoking-agent-returns-to-workflow} **Deliverables**: Refactored codebase + Mikado {visualization} documentation
Examples
Example 1: Extract shared domain model
/nw-mikado "Extract shared domain model from monolithic service layer"
Crafty builds Mikado dependency {visualization} through iterative exploration, discovers 12 leaf nodes across 4 modules, executes bottom-up from leaves to goal with discovery commits at each step.
Expected Outputs
docs/mikado/{goal-name}.mikado.md
src/* (refactored implementation)
Discovery-tracking commits in git logAI agents that guide you from idea to working code, with human judgment at every gate. nWave runs inside Claude Code. It breaks feature delivery into seven waves (discover, diverge, discuss, design, devops, distill, deliver).
Repo: nWave-ai/nWave
Other commands on nwave.
- /buddy
nWave concierge — ask any question about methodology, project state, commands, migration, or troubleshooting. Read-only, contextual answers.
Open command - /bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD
Open command - /continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
Open command - /deliver
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
Open command - /design
Designs system architecture with C4 diagrams and technology selection. Use when defining component boundaries, choosing tech stacks, or creating architecture documents.
Open command - /devops
Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.
Open command

