architecture decider

The problem

Vague product requirements often stall development when architects spend too much time asking stakeholders for technical preferences they don't have. Developers need to move from a business idea to a concrete, costed infrastructure plan without getting trapped in endless "PostgreSQL or MySQL?" debates.

What it does

• Decomposes high-level business needs into quantifiable technical targets like QPS, data volume, and SLA requirements.
• Generates three distinct architectural blueprints: Fast Delivery (MVP), Balanced (Growth), and High-Performance (Enterprise).
• Produces a detailed comparison table covering tech stacks, person-months of effort, and granular infrastructure costs.
• Delivers an opinionated final recommendation with a specific scaling roadmap and migration triggers.
• Summarizes the entire technical plan into a business-language Executive Brief for non-technical stakeholders.

Why this beats prompting it yourself

Generic prompts result in generic advice or annoying follow-up questions. This skill forces autonomous decision-making and provides actual dollar-amount cost estimates based on 2026 cloud pricing baselines. It handles the tedious translation between deep technical specs and business-ready executive summaries automatically.

Use cases

• Architecting a cross-border payment reconciliation system with strict data retention.
• Designing a real-time analytics dashboard for high-concurrency event tracking.
• Planning a backend migration from a serverless MVP to a balanced container-based growth stack.
• Drafting a technical proposal for investors that includes both deep-dive specs and a 3-minute business summary.

Known limitations

Requires the presence of a 2026 pricing reference file for accurate cost estimation. It is not intended for simple library usage questions or debugging existing code.