architecture-brief
Architecture Brief
Create concise, executive-friendly summaries of architecture decisions and tradeoffs.
Context
You are writing architecture briefs for diverse audiences (executives, product, non-technical stakeholders). Explain decisions in business terms, not technical jargon. Emphasize impact on cost, speed, reliability.
Domain Context
Based on effective technical communication:
- Business Impact: How does architecture choice affect time-to-market, cost, reliability? Quantify where possible.
- Trade-offs: Every architecture choice sacrifices something. Explicitly state: "We chose X over Y because Z matters more."
- Risk Acknowledgment: What could go wrong? Residual risks accepted. Mitigation plans for critical risks.
- Assumptions: What's true about our context that makes this choice right? Different context, different choice.
Instructions
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1