system-architect

Analyze system architecture and generate incremental migration plans from PlantUML diagrams.

25|5|Updated Jun 15, 2024
One-click install
npx skills add https://github.com/OreStudio/OreStudio --skill system-architect-orestudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/OreStudio/OreStudio/tree/main/.claude/skills/system-architect
Command: npx skills add https://github.com/OreStudio/OreStudio --skill system-architect-orestudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps architecture teams analyze complex systems and plan incremental migrations that minimize risk and downtime.

Core Features & Use Cases

  • System-wide architectural planning: Create migration roadmaps that span multiple components and layers.
  • Diagram-driven analysis: Interpret system and component diagrams to identify impact.
  • Migration governance: Generate a structured TODO list and plan with traceable steps.

Quick Start

Run the system-architect skill to draft an incremental migration plan for the current architecture.

Frequently Asked Questions about system-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan an incremental migration for a multi-component system refactor?

Plan an incremental migration by analyzing system architecture and generating a structured roadmap. This approach minimizes risk and downtime by creating traceable steps across Foundation, Infrastructure, Domain, and Application layers.

Can I use PlantUML diagrams to analyze system architecture impact?

Yes, you can use PlantUML diagrams to analyze system architecture. The process reads system and component diagrams, such as projects/modeling/ores.puml, to identify impact and updates diagrams alongside related documentation.

What is the best way to govern a system-wide migration plan?

The best way to govern a system-wide migration plan is to generate a structured TODO list with traceable steps. This ensures incremental migrations across multiple components remain trackable and minimize downtime.

How do you introduce cross-cutting concerns across multiple architectural layers?

Introduce cross-cutting concerns by applying incremental migration plans spanning Foundation, Infrastructure, Domain, and Application layers. This structured evolution of architectural patterns minimizes system-wide disruption.

Does analyzing system architecture for migration require existing component diagrams?

Yes, analyzing system architecture for migration requires existing component diagrams. The process reads system diagrams to identify impact and generates an incremental migration plan based on those visual inputs.

When should I not use an incremental migration approach for system changes?

Avoid an incremental migration approach for simple, isolated component changes. This architectural planning method is designed for multi-component refactors and evolving cross-cutting concerns across multiple layers.