/nw-mikado
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking
Claude Code
$ npx -y skills add nWave-ai/nWave --skill nw-mikado --agent claude-code
Codex
$ npx skills add nWave-ai/nWave --skill nw-mikado -a codex -y
Cursor
$ npx skills add nWave-ai/nWave --skill nw-mikado -a cursor -y
Gemini CLI
$ npx skills add nWave-ai/nWave --skill nw-mikado -a gemini-cli -y
GitHub Copilot
$ npx skills add nWave-ai/nWave --skill nw-mikado -a github-copilot -y
OpenCode
$ npx skills add nWave-ai/nWave --skill nw-mikado -a opencode -y
Windsurf
$ npx skills add nWave-ai/nWave --skill nw-mikado -a windsurf -y
SKILL.md
nw-mikado.SKILL.mdname: nw-mikado
description: "[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking"
user-invocable: true
argument-hint: '[refactoring-goal] - Optional: --complexity=[simple|moderate|complex] --visualization=[tree|graph]'
> **Code facts** — resolve structural facts about code through `code-fact` CLI (vendor-neutral, bundled adapters: AST then TextSearch). Degrade LOUD. Never ad-hoc grep. Example: `code-fact query.callers-of SYMBOL --root ROOT`.
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
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
name: nw-mikado description: "[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking" user-invocable: true argument-hint: '[refactoring-goal] - Optional: --complexity=[simple|moderate|complex] --visualization=[tree|graph]'
> **Code facts** — resolve structural facts about code through `code-fact` CLI (vendor-neutral, bundled adapters: AST then TextSearch). Degrade LOUD. Never ad-hoc grep. Example: `code-fact query.callers-of SYMBOL --root ROOT`.
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
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).
Other skills on nwave.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about nw-mikado.
- Which coding agents can use nw-mikado?
- nw-mikado installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

