nw-mikado

Plan complex refactoring projects by applying the Mikado Method to visualize dependencies and guide bottom-up leaf-node implementation. It generates a visualization file in docs/mikado to track iterative discovery commits and verify tests.

The Mikado Method is a technique for architectural changes that visually maps dependencies to identify leaf tasks. You implement these bottom-up tasks iteratively, recording exploration commits until the refactoring goal is fully satisfied.

You visualize code dependencies by generating a lightweight markdown file in docs/mikado for each refactoring goal. This visualization tracks progress and records iterative discovery commits as you work toward the finished goal.

Yes, this approach specifically guides architectural changes spanning multiple classes or services. It applies bottom-up leaf-node implementation and iterative discovery to manage complex multi-class refactoring workflows effectively.

Track iterative refactoring progress by recording discovery commits and generating a dedicated visualization document under docs/mikado. This provides proof of progress and ensures verified tests accompany the finished goal.

Use bottom-up implementation when planning complex refactors with deep dependencies. The Mikado Method helps you identify and implement leaf nodes first, iteratively discovering requirements and recording commits until the overarching architectural goal is met.