skill-platform-architecture-decisions
Make confident platform architecture decisions with structured analysis
What You Can Do
This skill guides you through systematic evaluation of platform architecture options by analyzing trade-offs, scalability implications, and long-term maintenance costs. You'll generate decision matrices, risk assessments, and implementation roadmaps for critical architecture choices like microservices vs monolith, cloud providers, database strategies, and caching layers.
Features
Automatically create weighted comparison matrices for competing architecture approaches, scoring each option against criteria like scalability, cost, team expertise, and time-to-market.
Evaluate hidden costs and benefits of each architecture choice—latency vs consistency, flexibility vs operational overhead, innovation speed vs stability.
Project how each architecture scales with users, data volume, and transaction throughput, identifying breaking points and mitigation strategies.
Systematically identify technical, operational, and organizational risks for each approach with severity ratings and mitigation tactics.
Generate phased rollout plans showing migration paths, rollback procedures, and success metrics for transitioning to new architectures.
Model infrastructure, licensing, and team resource costs across architecture options over 1-3 years, accounting for scaling and growth scenarios.
Produce a shareable, executive-ready decision document summarizing the analysis, recommendation, and rationale for stakeholder buy-in.
Example Output
Decision Matrix: Monolith vs Microservices
| Criterion | Weight | Monolith | Microservices |
|---|---|---|---|
| Time to Market | 25% | 9/10 | 5/10 |
| Scalability | 25% | 4/10 | 9/10 |
| Operational Complexity | 20% | 8/10 | 3/10 |
| Team Velocity (Year 2+) | 20% | 5/10 | 8/10 |
| Cost @ 1M Users | 10% | 6/10 | 7/10 |
| Weighted Score | 6.4 | 6.8 |
Key Risks for Microservices
- Distributed debugging complexity (High severity, Medium likelihood) → Mitigation: Invest in centralized logging and tracing from day one
- Network latency between services (Medium severity, High likelihood) → Mitigation: Implement aggressive caching; design services around communication boundaries
Migration Phase 2 (Months 4-6)
- Decompose auth service from monolith, run in parallel
- Implement service-to-service messaging layer
- Success metric: P99 latency < 50ms between services
What's Included
- Architecture Comparison Templates: Pre-built decision frameworks for common choices: monolith vs microservices, SQL vs NoSQL, single-region vs distributed, sync vs async messaging.
- Trade-off Analysis Checklist: Structured prompts to surface hidden costs, performance implications, and team impact factors you might otherwise miss.
- Scalability & Cost Models: Spreadsheet-ready projections for user growth, data volume, infrastructure costs, and team sizing across different architectures.
- Risk Assessment Taxonomy: Categorized risk library covering technical, operational, security, and organizational dimensions with severity/likelihood scoring.
- Implementation Roadmap Template: Phase-based rollout plan with milestones, rollback procedures, and success metrics to guide your team through transitions.
Who It's For
- Platform Architects
- Engineering Leads and CTOs
- Technical Decision-Makers
- Infrastructure & DevOps Teams
- Startup Founders (Technical)
Best For
- Evaluating monolith vs microservices tradeoffs
- Selecting databases and caching strategies
- Planning cloud provider migration
- Designing system reliability and scalability
- Building stakeholder consensus on architectural choices
You might also like
This skill helps you architect platform strategy by generating decision frameworks, prioritization matrices, and roadmap plans that account for developer ecosystem impact. You'll analyze tradeoffs between breaking changes, feature velocity, and technical debt to make confident platform decisions. It synthesizes developer feedback, competitive positioning, and business goals into actionable strategic outputs that your team can execute.
You can trace Claude's decision-making process step-by-step through the Agent Execution Loop, seeing exactly which skills were matched, what was expected, which tools were called, how results were verified, and what was learned. Generate an interactive HTML review page where you write targeted feedback next to each execution step, then feed that structured feedback back into Claude for iterative improvements.
by vcasecnikovs
You can model the complete ecosystem for any marketplace—mapping stakeholder incentives, transaction flows, and failure modes. This skill helps you stress-test platform designs against real-world scenarios, optimize pricing models that align buyer and supplier incentives, and identify regulatory or competitive risks before launch. You'll work through structured frameworks that capture ecosystem complexity and move from strategic design to implementation-ready specifications.
by mkatogui
Create comprehensive quarterly product roadmaps that balance feature development, bug fixes, and technical debt paydown across multiple teams. The skill maps explicit dependencies to surface blockers early, allocates finite resources realistically across work types, and assesses risk mitigation strategies for each initiative—then generates tailored communication templates for leadership reviews, customer updates, and team standups.
by az9713