Forge-Solution-Architecture

Designs technology-independent solution architectures from validated requirements and project context.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-solution-architecture-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Solution-Architecture
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/02-Architecture/Forge-Solution-Architecture
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-solution-architecture-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about Forge-Solution-Architecture

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

FAQPage Schema
How do I create a solution architecture document from requirements?▼

Follow the seven-step procedure: understand requirements, define system context, identify major components, define interactions, evaluate architectural options, identify risks, then produce the Architecture Definition using the provided template.

What should a software architecture definition include?▼

It should include an architecture overview, system context, component model, system boundaries, data flow description, integration overview, architectural considerations, risks, open questions, and a recommended approach.

When should I not do solution architecture work?▼

Skip it when requirements are not yet understood, the change is small and isolated, implementation details are already established, or only a coding-level design decision is needed.

Does solution architecture require choosing specific technologies?▼

No. The approach is technology-independent, focusing on capabilities, responsibilities, and structure before implementation technologies. Technology selection requires justification and typically happens in detailed design.

How does solution architecture relate to architecture decision records?▼

Significant architectural choices made during solution design are captured separately as Architecture Decision Records, while threat modelling and data modelling skills handle security risks and information structures.