Topology Planning

topology-planning

Turn a discovery summary into a target architecture and a phased, low-risk migration plan with ADRs.

When to use

After legacy-discovery, when defining the target state. Triggers: target architecture, migration plan, topology, modernization plan.

Inputs

• discovery_summary (string, required) — summary of the current system.
• target_style (string, optional) — microservices | modular-monolith | serverless.

Outputs

• migration_plan_markdown — principles, ADRs, phased plan, risk table.
• phases — ordered phase objects {id, name, goal}.

How it works

Selects a principle set for the chosen style and assembles a strangler-fig migration across four phases with a risk/mitigation table.

User stories

• As an architect, I get a defensible target architecture and an incremental path, not a big-bang rewrite.

Edge cases

• Unknown target_style → defaults to microservices.
• Empty summary → plan still renders with prompts to fill in.

Files

See DOCS.md.