skills.rest
JHaugaard
JHaugaardCOMMUNITY
Explore all skills by this author →
GitHub

solution-architect

Resolve architectural ambiguity in project briefs and generate architecture-context.json.

Updated Dec 5, 2025
Search Tags:#workflow#architecture#requirements#handoff#architecture-context.json
One-click install
npx skills add https://github.com/JHaugaard/refine-workflow-skills --skill solution-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solution-architect
Source: https://github.com/JHaugaard/refine-workflow-skills/tree/main/architect-skill
Command: npx skills add https://github.com/JHaugaard/refine-workflow-skills --skill solution-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

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."

Frequently Asked Questions about solution-architect

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

FAQPage Schema
How do I clarify architectural requirements before choosing a tech stack?▼

Architectural clarification resolves ambiguity in project briefs by asking targeted questions about scope (greenfield vs. brownfield), platform, integration needs, scale, and team constraints. This produces a structured architecture-context.json that guides tech-stack decisions downstream and prevents misaligned technology choices.

What questions should I answer to define my project's architecture?▼

Solution-architect asks about project type (new build, existing system, migration), target platforms, external integrations, expected scale, team size and skills, and technical constraints. These answers populate architecture-context.json with project_context, platform, integrations, scale, team, and constraints fields that constrain downstream tech recommendations.

When should I resolve architecture ambiguity in my project brief?▼

Resolve architectural ambiguity early—before selecting technologies. Briefs lacking specifics on greenfield/brownfield status, platform, integrations, scale, or team context create risk of misaligned stack choices. Architecture resolution generates a handoff document that enables precise, justified tech-stack recommendations.

What does architecture-context.json contain and how do I use it?▼

Architecture-context.json is a structured handoff document containing project_context, platform, integrations, scale, team, constraints, architecture_implications, and decisions_locked fields. It feeds directly into tech-stack-advisor and deployment-advisor to ensure downstream skills respect architectural decisions already made.

Can solution-architect work with an existing project brief file?▼

Yes. Provide your brief.json and request solution-architect to analyze it and generate architecture-context.json. The Skill identifies missing architectural details, asks clarifying questions, and produces a structured output ready for downstream Skills in the workflow.

What's the difference between greenfield, brownfield, and migration projects?▼

Greenfield is a new project with no legacy constraints; brownfield is building within an existing system; migration is moving or refactoring an existing system. Solution-architect classifies your project type because each demands different architectural considerations, platform choices, and integration strategies.

Related Skills

Explore More Software Engineering Skills→
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
anotherbenanotherben
6

enterprise-stack-review

Analyze TDD and stack profile to generate locked stack-decisions.json.

Community
Advanced
NirusanNirusan
7

tech-stack

Analyze project requirements and propose a technology stack in ADR format.

Community
Intermediate
tiantientiantien

blade-storm

Turn vague feature ideas into structured technical design documents.

Community
Advanced