design_options

Define and evaluate Build/Buy/Hybrid design options from requirements into JSON and Markdown reports.

40|15|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/chaussky/ainalyst --skill design-options
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design_options
Source: https://github.com/chaussky/ainalyst/tree/main/skills/design_options
Command: npx skills add https://github.com/chaussky/ainalyst --skill design-options

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Define and synthesize design options (Build/Buy/Hybrid) from gathered requirements to guide architecture decisions and enable informed solution selection.

Core Features & Use Cases

  • Create 2–3 design options for a project with components, improvement opportunities, and success metrics.
  • Allocate requirements across versions (v1, v2, out_of_scope) and benchmark options against standard criteria and custom weights.
  • Produce a Design Options Report (7.5/7.6) and align with the Change Strategy to support stakeholder decisions.

Quick Start

Set your change strategy, generate 3 design options, auto-allocate requirements, compare them, and save the final design options report.

Frequently Asked Questions about design_options

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

FAQPage Schema
How do I evaluate build, buy, or hybrid design options for architecture decisions?

You can evaluate build, buy, or hybrid design options by generating 2–3 approaches, allocating requirements across versions, and benchmarking them against standard criteria with custom weights to produce a design options report.

What is the best way to allocate requirements across design versions during solution selection?

Auto-allocating requirements into v1, v2, and out_of_scope categories allows you to map gathered requirements across multiple design versions, ensuring alignment with the change strategy for informed architecture decisions.

How does a design options report support stakeholder decisions in business architecture?

A design options report supports stakeholder decisions by benchmarking 2–3 build, buy, or hybrid approaches against weighted criteria, mapping success metrics, and aligning with the change strategy to recommend an informed architecture solution.

Can I benchmark architecture options against custom weights when requirements are known?

Yes, when requirements are known, you can benchmark 2–3 architecture options against standard criteria and custom weights. This comparison evaluates components and improvement opportunities to output a final solution recommendation.

What inputs do I need to generate a design options report for solution selection?

Generating a design options report requires inputs such as the traceability repo, prioritization, business context, architecture, and change strategy files to provide the known requirements needed to define and evaluate build, buy, or hybrid solutions.