topology-planning
Skill2 starsChanged 5 months agoMITView on GitHub
Generate a target architecture and migration plan from a discovery summary. Produces a migration_plan.md with target topology, ADRs, phased strategy, and risks. Trigger on: target architecture, migration plan, topology, modernization plan.
In this repository15 other files it gives its agents.
- change-impact-analysisSkill
- legacy-discoverySkill
- spec-governanceSkill
- task-decompositionSkill
- test-generationSkill
- ui-modernizationSkill
- jira-ticketSkill
- servicenow-ticketSkill
- speckit-constitutionSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- my-skillSkill
- text-statisticsSkill
- xquik-social-dataSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
After legacy-discovery, when defining the target state.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 tomicroservices. - Empty summary → plan still renders with prompts to fill in.
Files
See DOCS.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

