nWave/skills/nw-mikado/SKILL.md
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking
npx skillsauth add nwave-ai/nwave nw-mikadoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
EXPERIMENTAL: Under active development. Behavior and output format may change between versions.
Wave: CROSS_WAVE
Agent: Crafty (nw-software-crafter)
Command: *mikado
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.
@nw-software-crafter
Execute *mikado for {refactoring-goal}.
Context Files:
Configuration:
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").
Handoff To: {invoking-agent-returns-to-workflow} Deliverables: Refactored codebase + Mikado {visualization} documentation
/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.
docs/mikado/{goal-name}.mikado.md
src/* (refactored implementation)
Discovery-tracking commits in git log
testing
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
testing
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
development
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths)