mirror of
https://github.com/anthropics/claude-plugins-official.git
synced 2026-06-13 22:26:03 -03:00
bec8d7c93a
Viewer (assets/topology-viewer.html): - inline a minified d3 subset (hierarchy/pack, zoom, selection, interpolateZoom, ease; ISC license) instead of loading from a CDN — the page is now fully self-contained and works on air-gapped networks - handle duplicate node ids (unique-suffix; edges bind to the first occurrence) and store parent references directly, fixing level-of-detail and selection corruption with messy generated data - share one reveal rule between drawing, edge culling, and hit-testing so edges no longer draw into collapsed containers - pre-bucket edges by kind and keep a per-node adjacency map; the hover/selection pass no longer scans every edge each frame - cancel in-flight fly-to animations when a new one starts; clamp fly-to zoom to the zoom extent; derive max zoom from the smallest leaf so deep estates stay reachable - render dead-end candidates (new deadEnds field) with a dashed outline and a sidebar badge - clicking a node during a flow walkthrough exits the walkthrough; search results clear on selection and Escape; surrogate-safe label truncation; clearer stats line; explicit empty-topology message Commands: - new /modernize-status: read-only progress report — artifact inventory with timestamps, staleness flags, secrets-hygiene checks, next step - map: deadEnds in the topology schema; datastore names must be logical identifiers with credentials stripped from URLs/DSNs - brief: read topology.json + .mmd files (not the interactive HTML); staleness check against inputs; effort unit aligned to person-months - transform: secret-safe characterization-test prompt; diff -y fallback when delta is missing; credential-safe diff selection - reimagine: target vision is everything after the first argument (was silently truncated to one word); masking rules in spec/scaffold/ handoff prompts - brief/transform/reimagine: human-approval gates phrased as explicit stop-and-wait instead of 'enter plan mode' - preflight: delta in the tool table; brief added to the verdict list - README: preflight/status in the workflow; legacy/ deny list also covers Write; plugin + marketplace descriptions updated
97 lines
4.5 KiB
Markdown
97 lines
4.5 KiB
Markdown
---
|
|
description: Multi-agent greenfield rebuild — extract specs from legacy, design AI-native, scaffold & validate with HITL
|
|
argument-hint: <system-dir> <target-vision>
|
|
---
|
|
|
|
The first token of `$ARGUMENTS` is the system dir (`$1`); **everything
|
|
after it is the target vision** — it is usually multiple words, so do not
|
|
truncate it to one token. Below, `<vision>` means that full remainder.
|
|
|
|
**Reimagine** `legacy/$1` as: <vision>
|
|
|
|
This is not a port — it's a rebuild from extracted intent. The legacy system
|
|
becomes the *specification source*, not the structural template. This command
|
|
orchestrates a multi-agent team with explicit human checkpoints.
|
|
|
|
## Phase A — Specification mining (parallel agents)
|
|
|
|
Spawn concurrently and show the user that all three are running:
|
|
|
|
1. **business-rules-extractor** — "Extract every business rule from legacy/$1
|
|
into Given/When/Then form. Output to a structured list I can parse."
|
|
|
|
2. **legacy-analyst** — "Catalog every external interface of legacy/$1:
|
|
inbound (screens, APIs, batch triggers, queues) and outbound (reports,
|
|
files, downstream calls, DB writes). For each: name, direction, payload
|
|
shape, frequency/SLA if discernible. Mask any credential embedded in
|
|
endpoints or payload examples per your secret-handling rules."
|
|
|
|
3. **legacy-analyst** — "Identify the core domain entities in legacy/$1 and
|
|
their relationships. Return as an entity list + Mermaid erDiagram."
|
|
|
|
Collect results. Write `analysis/$1/AI_NATIVE_SPEC.md` containing:
|
|
- **Capabilities** (what the system must do — derived from rules + interfaces)
|
|
- **Domain Model** (entities + erDiagram)
|
|
- **Interface Contracts** (each external interface as an OpenAPI fragment or
|
|
AsyncAPI fragment)
|
|
- **Non-functional requirements** inferred from legacy (batch windows, volumes)
|
|
- **Behavior Contract** (the Given/When/Then rules — these are the acceptance tests)
|
|
|
|
Credential values are masked everywhere in the spec; connection details
|
|
appear as env-var placeholders (`${DATABASE_URL}`), never literals.
|
|
|
|
## Phase B — HITL checkpoint #1
|
|
|
|
Present the spec summary. Ask the user **one focused question**: "Which of
|
|
these capabilities are P0 for the reimagined system, and are there any we
|
|
should deliberately drop?" Wait for the answer. Record it in the spec.
|
|
|
|
## Phase C — Architecture (single agent, then critique)
|
|
|
|
Design the target architecture for "<vision>":
|
|
- Mermaid C4 Container diagram
|
|
- Service boundaries with rationale (which rules/entities live where)
|
|
- Technology choices with one-line justification each
|
|
- Data migration approach from legacy stores
|
|
|
|
Then spawn **architecture-critic**: "Review this proposed architecture for
|
|
<vision> against the spec in analysis/$1/AI_NATIVE_SPEC.md. Identify over-engineering,
|
|
missed requirements, scaling risks, and simpler alternatives." Incorporate
|
|
the critique. Write the result to `analysis/$1/REIMAGINED_ARCHITECTURE.md`.
|
|
|
|
## Phase D — HITL checkpoint #2
|
|
|
|
Present the architecture and **stop — scaffold nothing until the user
|
|
explicitly approves** (use plan mode if the session supports it).
|
|
|
|
## Phase E — Parallel scaffolding
|
|
|
|
For each service in the approved architecture (cap at 3 to keep the run
|
|
tractable; tell the user which you deferred), spawn a **general-purpose agent
|
|
in parallel**:
|
|
|
|
"Scaffold the <service-name> service per analysis/$1/REIMAGINED_ARCHITECTURE.md
|
|
and AI_NATIVE_SPEC.md. Create: project skeleton, domain model, API stubs
|
|
matching the interface contracts, and **executable acceptance tests** for every
|
|
behavior-contract rule assigned to this service (mark unimplemented ones as
|
|
expected-failure/skip with the rule ID). No credential literal from legacy
|
|
code becomes a test fixture or config default — use fake same-shape values
|
|
and env-var placeholders. Write to modernized/$1-reimagined/<service-name>/."
|
|
|
|
Show the agents' progress. When all complete, run the acceptance test suites
|
|
and report: total tests, passing (scaffolded behavior), pending (rule IDs
|
|
awaiting implementation).
|
|
|
|
## Phase F — Knowledge graph handoff
|
|
|
|
Write `modernized/$1-reimagined/CLAUDE.md` — the persistent context file for
|
|
the new system, containing: architecture summary, service responsibilities,
|
|
where the spec lives, how to run tests, and the legacy→modern traceability
|
|
map. This file IS the knowledge graph that future agents and engineers will
|
|
load — and it gets committed: connection details and credentials appear
|
|
only as env-var names with a pointer to where they're provisioned, never
|
|
as values.
|
|
|
|
Report: services scaffolded, acceptance tests defined, % behaviors with a
|
|
home, location of all artifacts.
|