solution-arch-agent

Assess platform feasibility and generate solution-design.md after customer specifications are approved.

13|12|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/itential/builder-skills --skill solution-arch-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solution-arch-agent
Source: https://github.com/itential/builder-skills/tree/main/.claude/skills/solution-arch-agent
Command: npx skills add https://github.com/itential/builder-skills --skill solution-arch-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a customer specification is approved, teams must determine what is possible on the live platform and define a concrete delivery plan. This skill automates that evaluation and produces the artifacts engineers rely on to proceed with implementation.

Core Features & Use Cases

  • Feasibility assessment grounded in the approved customer-spec and live platform data.
  • Generation of the design artifact (solution-design.md) including component inventory, adapter mappings, reuse decisions, build order, and test plan.
  • Design-only mode to adjust the design when requirements remain stable.
  • Handoff readiness to the builder-agent with approved feasibility and design artifacts.

Quick Start

Trigger this skill after a customer-spec is approved to generate feasibility.md and solution-design.md by connecting to the live platform and evaluating adapters and capabilities.

Frequently Asked Questions about solution-arch-agent

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

FAQPage Schema
How do I assess platform feasibility for an approved customer specification?▼

To assess platform feasibility, connect to the live platform, discover available adapters and capabilities, and validate them against the approved customer spec to produce a feasibility.md artifact for engineering handoff.

What is solution architecture design and how does it map adapters to requirements?▼

Solution architecture design defines a concrete delivery plan by mapping approved requirements to live platform adapters, determining reuse decisions, and generating a solution-design.md artifact for engineers.

How do I generate a solution design document after customer specs are approved?▼

Generate a solution design document by authenticating to the platform, evaluating discovered capabilities against the approved spec, and outputting solution-design.md with component inventory and build order.

Can I update a solution design without repeating the full platform feasibility assessment?▼

Yes, you can update a solution design without repeating platform feasibility by using a design-only mode, which adjusts the existing design artifacts when the customer requirements remain unchanged.

What is the best way to transition from feasibility assessment to engineering handoff?▼

The best way to transition to engineering handoff is to produce both feasibility.md and solution-design.md artifacts, ensuring builder-agent readiness with complete component inventory, adapter mappings, and test plans.

What limitations exist when automating solution architecture generation against a live platform?▼

Limitations include requiring platform authentication to discover adapters and capabilities, and needing an approved customer specification; design-only mode is restricted to cases where requirements remain unchanged.