architecture-options-analysis

Compare 2-4 architecture alternatives and recommend one with rejection reasons.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in preventing premature architectural convergence, facilitating thoughtful choice of a system's architecture by comparing realistic options with explicit rejection reasons.

Core Features & Use Cases

  • Realistic Options Analysis: Provides a comparison of 2-4 plausible architecture options tailored to specific constraints and needs.
  • Trade-off Analysis: Evaluates options based on factors like cost, risk, migration pain, and operational complexity.
  • Implementation Guidance: Offers a recommended architecture with a clear path to implementation.
  • Use Case: Ideal for planning large-scale system changes where choosing the wrong structure is expensive, such as architecture updates, major refactors, or migrations.

Quick Start

Trigger the skill by prompting, "Please analyze the architecture options for our upcoming project."

Frequently Asked Questions about architecture-options-analysis

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

FAQPage Schema
How do I compare software architecture options for a major system refactor?

Comparing architecture options for a system refactor involves evaluating 2-4 realistic alternatives against constraints like migration pain, complexity, and cost. This ensures you select an optimal structure by explicitly rejecting unsuitable options with clear trade-off reasons.

What is the best way to evaluate architecture trade-offs during a system design update?

Evaluating architecture trade-offs during a system design update requires assessing factors like cost, risk, migration pain, and operational complexity. Comparing multiple plausible options prevents premature architectural convergence and ensures a thoughtful, justified system structure selection.

When do I need to perform an architecture analysis before modifying system design?

You need to perform an architecture analysis when planning large-scale system changes where choosing the wrong structure is expensive. It is ideal for major refactors, architecture updates, or migrations to prevent premature convergence on a flawed design.

How do I choose the right software architecture for a complex migration?

To choose the right software architecture for a complex migration, compare 2-4 realistic alternatives tailored to your specific constraints. Evaluate migration pain and operational complexity to recommend a clear implementation path while explicitly discarding unsuitable options.

Can I use architecture options analysis to prevent premature convergence in system design?

Yes, architecture options analysis prevents premature convergence by facilitating a thoughtful choice of a system's structure. It compares realistic design options against specific constraints and explicitly documents the rejection reasons for unchosen alternatives.