metodologia-architecture-tobe

Design TO-BE architecture with C4 diagrams, ADRs, and Strangler Fig migration plans.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-architecture-tobe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: metodologia-architecture-tobe
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/architecture/architecture-tobe
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-architecture-tobe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The TO-BE Architecture skill enables enterprise teams to define a credible future-state architecture for modernization projects, anchored in AS-IS evidence, business constraints, and regulatory requirements while delivering actionable artifacts for safe migration.

Core Features & Use Cases

  • Produce C4 Level 2 TO-BE container diagrams and layer descriptions.
  • Create Architecture Decision Records (ADRs) and a 5+ nightmare scenarios with defense-in-depth mitigations.
  • Design MVP components, a phased Strangler Fig migration plan, and governance artifacts (RACI, Validation Gate).
  • Support executive and technical audiences with executive-friendly deliverables and technical depth as needed.

Quick Start

Provide a system description and an approved scenario to generate the TO-BE diagrams, ADRs, nightmare scenarios, MVP component, and migration plan.

Frequently Asked Questions about metodologia-architecture-tobe

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

FAQPage Schema
How do I design a TO-BE architecture for legacy system modernization?▼

TO-BE architecture design defines a credible future-state for enterprise modernization by producing C4 L2 container diagrams, ADRs, nightmare scenarios, and phased migration plans anchored in AS-IS evidence and business constraints.

What is the best way to plan a Strangler Fig migration for enterprise systems?▼

A Strangler Fig migration plan is designed by defining MVP components and phased migration steps, codifying operational patterns like CQRS, Saga, and Outbox within a robust Validation Gate to ensure safe legacy system replacement.

How do you document architecture decisions and risk mitigations for complex programs?▼

Architecture decisions and risks are documented by creating Architecture Decision Records (ADRs) alongside five or more nightmare scenarios with defense-in-depth mitigations to validate security and operational patterns.

Can I generate executive-friendly deliverables alongside technical architecture designs?▼

Yes, TO-BE architecture design supports both executive and technical audiences by delivering executive-friendly governance artifacts like RACI matrices alongside technical depth such as C4 L2 diagrams and mTLS deployment patterns.

When do I need CQRS, Saga, and Outbox patterns in a migration plan?▼

CQRS, Saga, and Outbox patterns are needed in a migration plan when codifying security, deployment, and operational requirements within a robust Validation Gate for complex enterprise modernization programs.