solution-architect

Translate business requirements into enterprise architectures using TOGAF, ADRs, and trade-off analysis.

8|11|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/belokonm/claude-supercode-skills --skill solution-architect-belokonm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-architect
Source: https://github.com/belokonm/claude-supercode-skills/tree/main/solution-architect-skill
Command: npx skills add https://github.com/belokonm/claude-supercode-skills --skill solution-architect-belokonm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns business strategy with technology choices by providing a structured approach to designing enterprise-scale solutions, reducing risk from misalignment and scope creep.

Core Features & Use Cases

  • Architecture guidance and governance using TOGAF, ADRs, and trade-off analysis to select options that satisfy business and technical requirements.
  • End-to-end solution design: reference architectures, integration strategies, data flows, and non-functional requirements mapping to roadmaps.
  • Use Case: When launching a multi-system program, produce architecture decisions, select technologies, and define a phased roadmap that ensures scalability, security, and operability.

Quick Start

Ask the AI to draft a high-level enterprise solution architecture for a new initiative, outlining major components, integration points, and governance artifacts.

Frequently Asked Questions about solution-architect

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

FAQPage Schema
How do I translate business requirements into enterprise-scale solution architecture?

To translate business requirements into enterprise-scale solution architecture, this Skill applies TOGAF-inspired practices and trade-off analysis to design reference architectures, integration strategies, and data flows. It maps non-functional requirements to roadmaps, producing structured architecture decisions and governance artifacts that ensure scalability and maintainability.

When do I need architecture decision records for technology evaluation?

You need architecture decision records (ADRs) for technology evaluation when launching multi-system programs that require structured decisions and documentation. ADRs capture trade-off analysis and governance choices, ensuring technology selection aligns with enterprise standards and reducing the risk of scope creep or misalignment.

What is the best way to design integration patterns for enterprise architecture?

The best way to design integration patterns for enterprise architecture is to perform end-to-end solution design that defines major components, integration points, and data flows. Applying structured trade-off analysis ensures the integration strategy satisfies both business and technical requirements while maintaining scalability.

How do I apply TOGAF practices to guide technology choices and governance?

You apply TOGAF practices to guide technology choices and governance by using a structured approach to architecture design. This Skill leverages TOGAF-inspired frameworks to align tech strategy with business goals, producing governance artifacts and phased roadmaps that ensure operability, security, and enterprise standard compliance.

Does this approach work for designing reference architectures and phased roadmaps?

Yes, this approach works for designing reference architectures and phased roadmaps by mapping non-functional requirements to implementation phases. It supports multi-system programs by defining major components and integration points, ensuring the resulting roadmap guarantees scalability, security, and operability across the enterprise.