solution-architect

Generates architecture decision records, API contracts, data models, and project scaffolds from scale constraints.

176|49|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/nagisanzenin/production-grade --skill solution-architect-nagisanzenin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solution-architect
Source: https://github.com/nagisanzenin/production-grade/tree/main/skills/solution-architect
Command: npx skills add https://github.com/nagisanzenin/production-grade --skill solution-architect-nagisanzenin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing a system architecture without knowing scale, team size, budget, or compliance constraints leads to over-engineered or under-built systems. This Skill derives the architecture from your actual constraints through a structured discovery interview, then produces the full set of architecture deliverables. ## Core Features & Use Cases - Constraint-Driven Architecture: Runs a fitness function over scale, team size, budget, data patterns, and compliance requirements to select monolith, modular monolith, or microservices patterns. - Complete Deliverable Set: Generates ADRs, C4 Mermaid diagrams, tech-stack rationale, OpenAPI 3.1/gRPC/AsyncAPI contracts, ERDs, SQL migrations, and a Dockerized service scaffold at the project root. - Adaptive Engagement Modes: Supports Express, Standard, Thorough, and Meticulous discovery depths, from auto-deriving from a BRD to individual ADR approval with capacity cost modeling. - Use Case: A founder planning a SaaS expected to reach 50K users answers a short interview and receives a modular monolith design with service extraction plan, OpenAPI specs, migration files, and a runnable docker-compose scaffold. ## Quick Start Ask the assistant to design the system architecture for your product based on your expected user scale, team size, budget, and compliance requirements.

Frequently Asked Questions about solution-architect

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

FAQPage Schema
How do I choose between a monolith and microservices architecture?▼

The choice depends on scale and team size: under 1K users with 1-3 people favors a monolith, 1K-100K users with 3-15 people favors a modular monolith with a service extraction plan, and 100K+ users with 15+ people justifies microservices. This Skill runs that fitness function automatically from your interview answers.

What architecture deliverables does this Skill generate?▼

It generates ADRs, C4 context and container diagrams in Mermaid, a tech-stack rationale document, OpenAPI 3.1 or gRPC/AsyncAPI contracts, ERDs with SQL migration files, and a service scaffold with Dockerfiles, health checks, and docker-compose for local development.

Can it design architecture for an existing brownfield codebase?▼

Yes. In brownfield mode it reads the existing codebase context first, designs around current patterns, documents existing decisions in ADRs, and keeps API contracts backward-compatible rather than replacing working systems.

How does it handle compliance requirements like GDPR or HIPAA?▼

Compliance inputs feed the fitness function and change the architecture: GDPR adds data residency and right-to-deletion pipelines, HIPAA requires dedicated tenancy and encryption everywhere, SOC2 adds audit trails and RBAC, and PCI DSS mandates tokenization and network segmentation.

When should I not use microservices for a new project?▼

Avoid microservices for small teams or early-stage products under 100K users, since operational cost exceeds the benefit. Start with a modular monolith that documents service boundaries, and extract services only when team size or scale demands it.