nw-mikado

Plan and execute Mikado Method refactoring with commit-based discovery and docs/mikado progress.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-mikado-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-mikado
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-mikado
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-mikado-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans and executes complex refactoring tasks by applying the Mikado Method to deliver structured, incremental changes, reducing risk and improving traceability.

Core Features & Use Cases

  • Mikado-driven refactoring planning across modules
  • Visualizations of dependencies and progress (tree or graph)
  • Discovery-tracking via commits and bottom-up leaf-to-goal execution
  • Documentation of outcomes in docs/mikado

Quick Start

Initiate the Mikado workflow for your refactoring goal and let the system guide leaf-to-goal changes with chosen complexity and visualization.

Frequently Asked Questions about nw-mikado

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Mikado Method for refactoring and how does it work?

The Mikado Method is a structured approach to execute complex refactoring by mapping dependencies as a tree, then implementing changes incrementally from leaf nodes up to the goal to ensure traceable outcomes.

How do I plan incremental refactoring across multiple modules?

To plan incremental refactoring across modules, you initiate a Mikado workflow that guides leaf-to-goal changes, tracks discovery via commits, and stores progress documentation in the docs/mikado directory.

Can I visualize code dependencies and refactoring progress during the process?

Yes, you can visualize code dependencies and refactoring progress using tree or graph visualization options, which enforce requirements for context files and configurables to track bottom-up implementation.

Does this Mikado refactoring approach work for multi-class architectural changes?

Yes, the Mikado refactoring approach is explicitly applicable to multi-class architectural changes across modules, driving structured, incremental changes to reduce risk and improve traceability.

What is the best way to track refactoring discovery and outcomes in code?

The best way to track refactoring discovery is commit-based, using bottom-up leaf-to-goal execution that documents outcomes in docs/mikado, ensuring all incremental changes remain traceable.