Architecture Review Skill
Activation Context
Activates when discussing system architecture, design patterns, or making architectural decisions.
When to Invoke architect Agent
- •Designing new system components
- •Making technology stack decisions
- •Planning system integrations
- •Defining data flow architecture
- •Evaluating architectural trade-offs
- •Creating technical specifications
Coordination Protocol
Before Starting Architecture Work
- •Consult product-manager for requirements
- •Review existing architecture documentation in
/docs/architecture/ - •Check for existing ADRs in
/docs/decisions/
During Architecture Design
- •Create architecture diagrams (system, component, data flow)
- •Document design decisions with rationale
- •Consider scalability, performance, and security
- •Evaluate multiple alternatives
- •Coordinate with relevant engineers (backend, frontend, database)
Architecture Deliverables
- •System architecture diagram
- •Component design specification
- •Data flow documentation
- •Technology stack justification
- •ADR for significant decisions
Review Checklist
- • Scalability considered for 10x growth
- • Security architecture reviewed by security-engineer
- • Performance implications documented
- • Database schema reviewed by database-engineer
- • API contracts defined for backend-engineer
- • Frontend architecture aligned with frontend-engineer
- • DevOps deployment strategy with devsecopsengineer
- • Documentation created by documentation-engineer
Handoff Points
- •To backend-engineer: API specifications and business logic requirements
- •To frontend-engineer: UI architecture and component structure
- •To database-engineer: Data model and schema requirements
- •To devsecopsengineer: Infrastructure and deployment requirements
Best Practices
- •Document the "why" not just the "what"
- •Consider both current and future requirements
- •Evaluate cost vs. complexity trade-offs
- •Ensure architecture supports testing
- •Plan for monitoring and observability