What problem does it solve? Starting development without a defined architecture leads to unclear system boundaries, ad-hoc technical decisions, and unmaintainable systems. This Skill transforms validated requirements into a structured architectural blueprint before any code is written. ## Core Features & Use Cases - System Context & Boundaries: Defines what is inside and outside the system, including users, external systems, and major interactions. - Component Modeling: Identifies major components, their responsibilities, relationships, data flows, and integration points. - Risk & Option Evaluation: Compares architectural approaches with evidence-based reasoning and surfaces security, scalability, and operational risks. - Use Case: When starting a new project that must integrate with an existing payment gateway, use this Skill to produce an Architecture Definition document covering the component model, integration overview, risks, and recommended approach before implementation begins. ## Quick Start Use the Forge-Solution-Architecture skill to design a solution architecture for my project based on these functional and non-functional requirements.