Add the restructure skill, with the Mikado Method for stalled units

CLAUDE.md

@@ -20,7 +20,7 @@ planning the build with `plan-implementation`, sequencing it with `plan-a-phased
 `iterative-plan-review`, and questioning a stalled approach with `reassess-approach`, plus the `discussion-facilitator` agent that audits a planning discussion in progress;
 depends on `han-communication` and `han-core` and is bundled by the `han` meta-plugin),
 `han-coding` (the coding skills
-you reach for while working in code: writing it with `tdd` and `refactor`, designing an interface contract with
+you reach for while working in code: writing it with `tdd` and `refactor`, restructuring whole areas of it with `restructure`, designing an interface contract with
 `design-an-api`, plus reviewing, overviewing, analyzing,
 testing, investigating, and standardizing it with `code-review`, `code-overview`, `code-walkthrough`,
 `architectural-analysis`,
@@ -118,7 +118,7 @@ han-plugin-builder skill:
 │   ├── skills/         # Planning skill directories, each with SKILL.md + references/ + scripts/
 │   ├── docs/           # In-plugin long-form docs: docs/skills/{name}.md + docs/agents/discussion-facilitator.md
 │   └── references/     # Both kinds: han-planning-owned canonical files (planning-boundary-rule.md, scope-justification-rule.md, operator-escalation-rule.md, contract-pinning-rule.md, synthesis-failure-rule.md) beside vendored copies (yagni-rule.md, evidence-rule.md, config-rule.md, collaborative-stop-rule.md). Each owned file opens by saying so; do not overwrite one in a re-sync sweep
-├── han-coding/         # Coding plugin: tdd, refactor, design-an-api, code-review, code-overview, code-walkthrough, architectural-analysis, automated-test-planning, manual-test-planning, investigate, coding-standard (the skills for working in code; depends on han-communication and han-core; bundled by the han meta-plugin)
+├── han-coding/         # Coding plugin: tdd, refactor, restructure, design-an-api, code-review, code-overview, code-walkthrough, architectural-analysis, automated-test-planning, manual-test-planning, investigate, coding-standard (the skills for working in code; depends on han-communication and han-core; bundled by the han meta-plugin)
 │   ├── README.md       # Light front door + scent-line skills list
 │   ├── .claude-plugin/
 │   │   └── plugin.json
@@ -262,8 +262,8 @@ such as Claude, should be referenced here.
 - **[han-core/references/collaborative-stop-rule.md](./han-core/references/collaborative-stop-rule.md).** The shared
   contract behind `/pairing`: how a skill detects the collaborative flag, what a stop presents and in what order, when
   the pre-build ask fires and what makes a choice expensive to walk back, and what to do with the answer. Consumed by
-  `pairing` and by the skills that hand control back at their own boundaries — `tdd`, `refactor`, `design-an-api`,
-  `iterative-plan-review`, and `plan-implementation`. Vendored byte-identical into `han-coding/references/` and
+  `pairing` and by the skills that hand control back at their own boundaries — `tdd`, `refactor`, `restructure`,
+  `design-an-api`, `iterative-plan-review`, and `plan-implementation`. Vendored byte-identical into `han-coding/references/` and
   `han-planning/references/`; edit the canonical copy and re-sync the others.
 
 ### Writing voice

CONTRIBUTING.md

@@ -116,7 +116,7 @@ change goes before you scaffold anything. (For the user-facing version of this m
   job is specifying what a feature does, planning how to build it, sequencing the build, breaking it into work,
   stress-testing a plan before implementation, or questioning the approach a stalled plan commits to.
   It depends on `han-communication` and `han-core` and is bundled by the `han` meta-plugin.
-- **`han-coding`** carries the coding skills (`tdd`, `refactor`, `code-review`, `code-overview`,
+- **`han-coding`** carries the coding skills (`tdd`, `refactor`, `restructure`, `code-review`, `code-overview`,
   `architectural-analysis`, `automated-test-planning`, `manual-test-planning`, `investigate`, `coding-standard`). A skill goes here when its job is
   working directly in code: writing it, reviewing it, analyzing it, testing it, investigating it, or standardizing it.
   It depends on `han-communication` and `han-core` and is bundled by the `han` meta-plugin.

docs/concepts.md

@@ -244,7 +244,7 @@ plugins dispatch, the project-discovery skill, the `/pairing` collaborative work
 `/issue-triage`) plus the research-analyst agent. `han-planning` adds the planning skills you reach for before
 implementation (`/plan-a-feature`, `/plan-a-change`, `/plan-implementation`, `/plan-a-phased-build`,
 `/plan-work-items`, `/iterative-plan-review`, and `/reassess-approach`). `han-coding` adds the coding skills you reach for while working in code (`/tdd`, `/refactor`,
-`/design-an-api`, `/code-review`, `/code-overview`, `/code-walkthrough`, `/architectural-analysis`,
+`/restructure`, `/design-an-api`, `/code-review`, `/code-overview`, `/code-walkthrough`, `/architectural-analysis`,
 `/automated-test-planning`, `/manual-test-planning`, `/investigate`, and `/coding-standard`). `han-github` adds the GitHub skills, and `han-reporting` adds the reporting
 skills. All of these except `han-reporting` depend on `han-core`, so installing any of them brings the shared agents
 along; `han-reporting` depends only on `han-communication`.