solution-architect

What problem does it solve?

This Skill analyzes a project brief to resolve architectural questions before selecting a technology stack. It identifies whether the project is Greenfield, Brownfield, or Migration, defines target platforms, integration needs, scale expectations, and team context. It then produces a structured architecture-context.json that constrains downstream decisions for the tech-stack advisor.

Core Features & Use Cases

• Question-driven architecture: Asks targeted questions to resolve ambiguity in the brief.
• Handoff generation: Produces architecture-context.json to hand off to downstream skills.
• Non-prescriptive advisory: Documents decisions and rationale without prescribing specific tech choices.
• Workflow integration: Works between project-brief-writer and tech-stack-advisor in the Claude Skills chain.
• Use Case: A team has a vague "build a task tracker" brief—solution-architect clarifies platform, scale, and integrations, enabling precise stack recommendations.

Quick Start

Tell Claude your project brief (or provide brief.json) and ask to "initiate solution-architect" to produce architecture-context.json. For example: "Analyze my brief.json and generate architecture-context.json."