mirror of
https://github.com/anthropics/claude-plugins-official.git
synced 2026-06-13 22:26:03 -03:00
1c4a5cfded
modernize-map previously rendered the call graph and data lineage as static Mermaid diagrams, which become unreadable once a node has ~10+ edges — exactly the shape of real legacy systems. It now builds an interactive viewer from a shipped template (assets/topology-viewer.html): a zoomable circle-pack of domains/modules sized by LOC, rendered to canvas with level-of-detail reveal, dependency edges with per-kind toggles, search with fly-to, a per-node detail sidebar, and a flow walkthrough mode. Small domain-level .mmd exports remain for docs. - topology.json now has a documented schema (hierarchy + edges + entry points + observations + flows) consumed by the viewer - map traces 2-4 business flows anchored to personas (claimant, operator, auditor), each step in plain business language mapped to the modules that implement it; the viewer plays them as numbered paths - brief gains a Business Walkthroughs section connecting each persona flow to the phase that replaces it - new modernize-preflight command: detects the stack, checks analysis tooling, smoke-compiles a real source file with the legacy toolchain, inventories missing copybooks/descriptors/binary-only artifacts, and writes a per-command readiness verdict - transform now verifies legacy + target toolchains before its plan gate instead of failing at test time - README: commands updated, optional-tooling section reframed as 'what to give Claude'
75 lines
2.9 KiB
Markdown
75 lines
2.9 KiB
Markdown
---
|
||
description: Generate a phased Modernization Brief — the approved plan that transformation agents will execute against
|
||
argument-hint: <system-dir> [target-stack]
|
||
---
|
||
|
||
Synthesize everything in `analysis/$1/` into a **Modernization Brief** — the
|
||
single document a steering committee approves and engineering executes.
|
||
|
||
Target stack: `$2` (if blank, recommend one based on the assessment findings).
|
||
|
||
Read `analysis/$1/ASSESSMENT.md`, `analysis/$1/TOPOLOGY.html` (and the `.mmd`
|
||
files alongside it), and `analysis/$1/BUSINESS_RULES.md` first. If any are
|
||
missing, say so and stop — they come from `/modernize-assess`, `/modernize-map`,
|
||
and `/modernize-extract-rules` respectively. Run those first.
|
||
|
||
## The Brief
|
||
|
||
Write `analysis/$1/MODERNIZATION_BRIEF.md`:
|
||
|
||
### 1. Objective
|
||
One paragraph: from what, to what, why now.
|
||
|
||
### 2. Target Architecture
|
||
Mermaid C4 Container diagram of the *end state*. Name every service, data
|
||
store, and integration. Below it, a table mapping legacy component → target
|
||
component(s).
|
||
|
||
### 3. Phased Sequence
|
||
Break the work into 3-6 phases using **strangler-fig ordering** — lowest-risk,
|
||
fewest-dependencies first. For each phase:
|
||
- Scope (which legacy modules, which target services)
|
||
- Entry criteria (what must be true to start)
|
||
- Exit criteria (what tests/metrics prove it's done)
|
||
- Estimated effort (person-weeks, derived from COCOMO + complexity data)
|
||
- Risk level + top 2 risks + mitigation
|
||
|
||
Render the phases as a Mermaid `gantt` chart.
|
||
|
||
### 4. Business Walkthroughs
|
||
For each persona flow in `analysis/$1/topology.json` (`flows` — produced
|
||
by `/modernize-map`), a short narrative table: persona, what happens in
|
||
business language, which legacy modules implement it today, and which
|
||
phase from §3 replaces each. This is the section non-technical approvers
|
||
actually read — it connects "Phase 2" to "what happens when a customer
|
||
files a claim". If topology.json has no flows, derive 2–3 walkthroughs
|
||
from the entry points and say they need SME confirmation.
|
||
|
||
### 5. Behavior Contract
|
||
List the **P0 rules** from BUSINESS_RULES.md (the ones tagged `Priority: P0` —
|
||
money, regulatory, data integrity) that MUST be proven equivalent before any
|
||
phase ships. These become the regression suite. Flag any P0 rule with
|
||
Confidence < High as a blocker requiring SME confirmation before its phase
|
||
starts.
|
||
|
||
### 6. Validation Strategy
|
||
State which combination applies: characterization tests, contract tests,
|
||
parallel-run / dual-execution diff, property-based tests, manual UAT.
|
||
Justify per phase.
|
||
|
||
### 7. Open Questions
|
||
Anything requiring human/SME decision before Phase 1 starts. Each as a
|
||
checkbox the approver must tick.
|
||
|
||
### 8. Approval Block
|
||
```
|
||
Approved by: ________________ Date: __________
|
||
Approval covers: Phase 1 only | Full plan
|
||
```
|
||
|
||
## Present
|
||
|
||
Enter **plan mode** and present a summary of the brief. Do NOT proceed to any
|
||
transformation until the user explicitly approves. This gate is the
|
||
human-in-the-loop control point.
|