Consult Architect

Analyze system design trade-offs and deliver a structured architecture memo.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Row0902/agents --skill consult-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Consult Architect
Source: https://github.com/Row0902/agents/tree/main/.agent/skills/consult_architect
Command: npx skills add https://github.com/Row0902/agents --skill consult-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured guidance to software architects facing architectural decisions by analyzing trade-offs and identifying scalable design options.

Core Features & Use Cases

  • Trade-off analysis framework comparing design options
  • Actionable design memo deliverable
  • Best-fit patterns for scalable, maintainable systems

Quick Start

Describe your system goal and request a trade-off analysis with recommended architecture options.

Frequently Asked Questions about Consult Architect

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

FAQPage Schema
How do I analyze trade-offs for system design and scalability patterns?

A design memo documents architectural decisions by detailing trade-offs, recommended patterns, and separation of concerns. It captures scalable design principles and dependency inversion strategies to resolve decision bottlenecks and provide structured guidance for maintainable systems.

How do I structure a design memo for architecture decisions?

A design memo documents architectural decisions by detailing trade-offs, recommended patterns, and separation of concerns. It captures scalable design principles and dependency inversion strategies to resolve decision bottlenecks and provide structured guidance for maintainable systems.

What is the best way to choose scalable architecture patterns for a new system?

When facing architectural decision bottlenecks, use structured trade-off analysis to evaluate scalable patterns. This approach clarifies separation of concerns and dependency inversion, delivering a recommended architecture with clear principles to resolve complex system design choices.

Can I get architecture trade-off analysis for resolving scalability bottlenecks?

When facing architectural decision bottlenecks, use structured trade-off analysis to evaluate scalable patterns. This approach clarifies separation of concerns and dependency inversion, delivering a recommended architecture with clear principles to resolve complex system design choices.

When do I need dependency inversion and separation of concerns in system design?

You need dependency inversion and separation of concerns when designing scalable, maintainable systems requiring clear boundaries. Applying these architecture patterns through trade-off analysis ensures your system design accommodates growth and minimizes component coupling.