solution-architect

To decide on build vs buy for a software architecture, you need a formal analysis of total cost of ownership alongside risk and compliance factors. This Skill evaluates your project parameters to deliver a strategic-analysis report with a clear recommendation and 2-3 alternative options.

Documenting technology stack choices and security boundaries is best handled by generating a formal tech-and-security blueprint. This Skill produces a structured tech-and-security.md document defining allowed stacks, security boundaries, and compliance considerations for project governance.

Yes, you can generate a 3-year TCO analysis for evaluating a major system refactor. Provide the project path and required focus areas, and the Skill will calculate cost strategies and deliver a strategic-analysis plan to guide your architectural decision.

Macro-architectural planning for choosing between microservices, serverless, or monolithic patterns works by evaluating your specific project requirements. This Skill suggests suitable architectural patterns and defines bounded contexts to structure your system design effectively.

Yes, you need to provide your project path and required focus areas to generate an architecture blueprint. The Skill uses these inputs to identify the optimal technology stack, architecture pattern, and cost strategy, delivering documents with explicit assumptions and risk notes.

You should not use a formal solution architecture analysis when selecting trivial components that do not impact macro-architecture or require compliance evaluation. This Skill is designed for critical vendor selections, major refactors, and new projects needing comprehensive TCO and stack governance.