architecture

Coordinate phased architecture problem framing and adversarial review for system design.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/builtbylee/socratic-prompts --skill architecture-builtbylee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/builtbylee/socratic-prompts/tree/main/skills/architecture
Command: npx skills add https://github.com/builtbylee/socratic-prompts --skill architecture-builtbylee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Socratic architecture and systems-design orchestrator for high-stakes technical decisions. Use when designing new systems, reviewing architecture plans, selecting between competing approaches, planning migrations, or validating reliability/performance/security tradeoffs before implementation.

Core Features & Use Cases

  • Phase-based, structured problem framing and adversarial review workflow.
  • Supports requirement interrogation, risk analysis, and formal problem contracts before design.
  • Provides a repeatable process for deciding between architecture options, migrations, and reliability/safety tradeoffs.

Quick Start

Describe your system problem and constraints to begin Phase 1 of the workflow.

Frequently Asked Questions about architecture

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

FAQPage Schema
What is adversarial review in systems design?

Adversarial review in systems design is a structured process of rigorously interrogating requirements, analyzing risks, and validating reliability, performance, and security tradeoffs before implementation begins. It ensures formal problem contracts and explicit non-goals are established.

How do I plan a high-stakes system migration?

Plan a high-stakes system migration by applying a phased workflow that requires problem contracts, requirement interrogation, and measurable criteria. This structured approach validates competing architecture options and reliability tradeoffs before implementation starts.

Can I use this to select between competing architecture approaches?

Yes, you can use this structured workflow to select between competing architecture approaches. It coordinates problem framing and adversarial review to evaluate reliability, performance, and security tradeoffs, ensuring decisions are backed by measurable criteria.

What is the best way to validate architecture plans before implementation?

The best way to validate architecture plans is through a phased workflow imposing risk analysis and formal decision contracts. This method interrogates requirements and establishes measurable criteria to evaluate tradeoffs before any implementation begins.

How do I frame architecture problems for high-stakes technical decisions?

Frame architecture problems for high-stakes technical decisions by defining explicit non-goals and formal problem contracts. This Socratic orchestration approach structures requirement interrogation and risk analysis to fully evaluate design tradeoffs.

When should I not use a phased architecture workflow?

You should avoid a phased architecture workflow requiring formal problem contracts and risk analysis for low-stakes or trivial system modifications where rigorous tradeoff validation and measurable criteria provide unnecessary overhead.