solution-architect-skill_skill

This skill helps design enterprise-scale solutions by aligning technology with business goals, evaluating tradeoffs, and documenting architecture decisions.
  • Python

21

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill 404kidwiz/claude-supercode-skills --skill solution-architect-skill

  • SKILL.md3.6 KB

Overview

This skill provides expert guidance for designing high-level enterprise solutions that align technology with business strategy. It adapts architecture frameworks like TOGAF, performs trade-off analysis, and guides technology selection. The skill helps produce architecture decision records, integration patterns, and implementation roadmaps for enterprise initiatives.

How this skill works

The skill inspects business goals, functional and non-functional requirements, and existing enterprise architecture to generate candidate solution designs. It evaluates alternatives using weighted criteria, cost and risk analysis, and proof-of-concept results, then documents recommendations and ADRs. It produces integration patterns, data and security considerations, and phased implementation roadmaps tied to stakeholder outcomes.

When to use it

  • Designing an end-to-end solution for a new product or initiative
  • Comparing and selecting technology platforms or vendors
  • Creating architecture decision records (ADRs) and formalizing rationale
  • Ensuring alignment with enterprise architecture and compliance standards
  • Analyzing trade-offs for scalability, availability, security, and cost

Best practices

  • Start from business outcomes and derive technical requirements
  • Produce 2–3 viable candidate architectures and evaluate trade-offs
  • Document decisions and rationale in ADRs linked to requirements
  • Validate key assumptions early with prototypes or PoCs
  • Design for change: isolate volatile components and define clear interfaces

Example use cases

  • Define solution architecture for a customer-facing platform with high availability SLAs
  • Evaluate cloud vs. on-premises alternatives including TCO and exit costs
  • Design integration patterns for legacy systems and new microservices
  • Create ADRs for major technology choices and record consequences
  • Plan a phased implementation roadmap that reduces risk and preserves business continuity

FAQ

Define business-critical criteria, weigh TCO, time-to-market, vendor viability, and future flexibility; prefer PoC for high-risk items.

When should I use synchronous vs asynchronous integration?

Use synchronous for low-latency, transactional interactions; prefer asynchronous for loose coupling, resilience, and variable workloads.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational