architecture-debate

Frame architectural design decisions with options, trade-offs, and a formal decision note.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/kiran-capoor94/wizard --skill architecture-debate-kiran-capoor94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-debate
Source: https://github.com/kiran-capoor94/wizard/tree/main/src/wizard/skills/architecture-debate
Command: npx skills add https://github.com/kiran-capoor94/wizard --skill architecture-debate-kiran-capoor94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This section frames how teams make high-stakes architectural decisions by surfacing context, constraints, and trade-offs.

Core Features & Use Cases

  • Frame decisions with structured options and criteria.
  • Surface prior decisions and investigations to avoid rework.
  • Record and communicate recommendations and rationale for future sessions.

Quick Start

Provide two clear design options with trade-offs, cite constraints, and save the final decision note.

Frequently Asked Questions about architecture-debate

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

FAQPage Schema
How do I frame architectural trade-offs when making a design decision?

To frame architectural trade-offs, identify the design decision, surface prior context and constraints, and present at least two concrete options with their respective trade-offs for evaluation.

What's the best way to document rejected alternatives in an architecture decision record?

Document rejected alternatives by recording the final decision as a formal note, including the rationale and the specific options that were dismissed to guide future architectural work.

How do I provide technical guidance that compares design options for a software project?

Provide technical guidance by presenting multiple design options, comparing their trade-offs, and delivering a recommendation grounded in the specific constraints of the project.

Why do I need to surface prior context before evaluating new architecture options?

Surfacing prior context and past investigations is necessary to avoid rework and ensure that new architecture options address existing constraints rather than duplicating previous efforts.

Can I use this approach for any software engineering design decision?

Yes, framing decisions with structured options and criteria applies to any software engineering design decision where you need to evaluate constraints and choose between concrete options.

What should a formal architecture decision note include to guide future work?

A formal architecture decision note should include the final decision, its rationale, constraints considered, and any rejected alternatives to provide clear context for future work.