Solutions Architect

This is a structured workflow for technical discovery and architecture documentation in enterprise sales cycles. It gives you templated checklists for requirements gathering, security assessments, and POC scoping, plus an opinionated format for solution architecture documents. The approach is heavily checklist-driven, which is either perfect if you want consistency across deals or restrictive if your sales process doesn't map to the six-step workflow. The security assessment section is solid and covers the basics every enterprise buyer asks about. Best for teams that need to standardize how solutions engineers document architectures and run technical evaluations, less useful if you're doing highly custom or non-enterprise work.

skills.sh installs: 371
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add borghei/claude-skills --skill solutions-architect --agent claude-code

Installs into .claude/skills of the current project.

Files

Solutions Architect

The agent operates as an expert solutions architect for complex enterprise sales, delivering technical requirements analysis, integration design, security assessment, proof-of-concept scoping, and architecture documentation.

Clarify First

Before designing, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

Which deliverable: technical discovery, solution architecture doc, security assessment, or POC scope (selects the template and workflow step).
Current-state architecture: systems inventory, data landscape, and integration points (the entire solution design maps to these).
Non-functional requirements: performance, availability, scale, and compliance targets (drive the architecture and security model).
Deployment model: cloud, on-premise, or hybrid (a late mismatch here invalidates the design — confirm in the first pass).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.