design-analysis

Compares architecture options and produces bounded design recommendations with explicit trade-offs.

Updated May 22, 2026
One-click install
npx skills add https://github.com/handaeho/Harness_Engineering --skill design-analysis-handaeho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-analysis
Source: https://github.com/handaeho/Harness_Engineering/tree/main/prompt-stack/_candidates/v36_candidate/codex/skills/design-analysis
Command: npx skills add https://github.com/handaeho/Harness_Engineering --skill design-analysis-handaeho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architecture and design decisions often suffer from hidden trade-offs, unbounded option exploration, and recommendations stronger than their supporting evidence. This Skill structures high-stakes design work so options are compared on explicit axes, risks stay visible, and the final recommendation matches the actual evidence. ## Core Features & Use Cases - Bounded Option Comparison: Generates a small candidate set (conservative, default, higher-upside), prunes weak options, and compares them on decision-relevant axes like cost, latency, blast radius, and reversibility. - Planning and Review Gates: Enforces plan approval checkpoints for destructive, costly, or policy-sensitive recommendations, plus producer-critic reflection passes for high-impact designs. - Decision Packets and Close-Outs: Produces auditable artifacts such as routing decision memos, resource budget memos, and readiness memos, closing with one recommended path, one fallback, and one next validation step. - Use Case: When choosing between two service architectures for a migration, use this Skill to frame constraints, compare the options on maintainability and blast radius, and receive a recommendation with an explicit fallback and rollback plan. ## Quick Start Use the design-analysis skill to compare monolith versus microservices for our payment service migration and recommend a path with trade-offs and a fallback.

Frequently Asked Questions about design-analysis

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

FAQPage Schema
How do I compare architecture options with explicit trade-offs?

Define the goal, constraints, and a small set of decision axes such as cost, latency, blast radius, and reversibility, then compare only a few meaningful candidates. This Skill generates a conservative, default, and higher-upside option, prunes weak ones, and recommends the strongest path with a fallback.

When should I use a design analysis skill instead of direct coding?

Use it when multiple credible options compete, trade-offs materially matter, or the task is high-risk and dependency-heavy. Skip it for narrow local fixes, straightforward tasks, or short factual answers where direct execution is already reliable.

How do I write a technical decision memo for an architecture choice?

Frame the problem with hard constraints and risk tolerance, compare candidates on weighted axes, then close with one recommended path, one fallback, and one next validation step. The Skill supports routing decision memos and resource budget memos as auditable artifacts.

Can design recommendations trigger approval gates before execution?

Yes. When a recommended path involves destructive, costly, or policy-sensitive execution, the Skill presents the plan for review before recommending autonomous execution, and re-checks the review boundary if the plan changes materially.

What are the limitations of option comparison for design decisions?

Comparison quality depends on evidence strength; weak ownership maps, vague interface contracts, or missing operational baselines should lower recommendation strength. The Skill stops analysis when additional branches no longer change the decision and reroutes benchmark-gating questions to eval-ops.