Architect

Generate architectural proposals, rank them via tournament evaluation, and record ADRs.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/markusstrasser/skills --skill architect-markusstrasser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architect
Source: https://github.com/markusstrasser/skills/tree/main/archive/architect
Command: npx skills add https://github.com/markusstrasser/skills --skill architect-markusstrasser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decision-making often becomes slow and uncertain when teams juggle competing proposals, lack a structured ranking method, and struggle to record decisions. This Skill provides a repeatable flow that collects proposals from multiple providers, ranks them using tournament-based evaluation, and records decisions as ADRs to improve traceability.

Core Features & Use Cases

  • Generate proposals from multiple LLM providers (e.g., Gemini, Codex, Grok) to surface diverse architectural options.
  • Rank proposals via tournament-based evaluation to identify the strongest architectural direction.
  • Refine and record decisions as Architectural Decision Records (ADRs) for governance and future reference.
  • Use cases include comparing event-sourcing vs. CQRS designs, deciding between microservice patterns, and evaluating data-store strategies.

Quick Start

Run a full workflow with a problem description to generate proposals, rank them via tournament evaluation, and record the final ADR.

Frequently Asked Questions about Architect

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

FAQPage Schema
How do I make evidence-based architectural decisions when comparing competing designs?

Evidence-based architectural decisions are made by generating proposals from multiple LLM providers, ranking them via tournament-based evaluation, and recording the outcome as a structured ADR for traceability.

What's the best way to compare microservice patterns or event-sourcing vs. CQRS architectures?

Comparing microservice patterns or event-sourcing vs. CQRS involves gathering proposals from multiple LLM providers and using a tournament-based evaluator to identify and rank the strongest architectural direction.

How do I generate and rank architectural proposals from different LLM providers?

Generating and ranking architectural proposals requires submitting a problem description to collect options from multiple LLM providers like Gemini, Codex, and Grok, then ranking them through tournament-based evaluation.

Do I need Python and the llmx CLI to automate architectural decision-making?

Yes, automating architectural decision-making requires Python 3.10+, an API key, and access to the llmx CLI to generate proposals and execute the tournament-based ranking workflow.

Can I use this approach to evaluate data-store strategies and record them as ADRs?

Yes, you can evaluate data-store strategies by generating multiple proposals, ranking them using tournament-based evaluation, and refining the final choice into a recorded Architectural Decision Record (ADR) for governance.

How does tournament-based evaluation work for architectural decision records?

Tournament-based evaluation for architectural decision records works by pitting proposals from multiple LLM providers against each other to systematically rank competing designs and identify the most well-justified option.