/nw-mikado
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking
$ npx -y skills add nWave-ai/nWave --skill nw-mikado --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/nw-mikado
Context preview
The summary Claude sees to decide when to auto-load this skill.
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking
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]'
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]'
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).
Repo: nWave-ai/nWave
Other skills on nwave.
- /nw-ab-critique-dimensions
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Open skill - /nw-abr-critique-dimensions
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
Open skill - /nw-ad-critique-dimensions
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof
Open skill - /nw-agent-creation-workflow
Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement
Open skill - /nw-agent-testing
5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance
Open skill - /nw-architectural-styles-tradeoffs
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.
Open skill

