saranskumar Goal
Review systems at the architecture and operations level, not just the code level.
When to Use
- A design spans several components or runtimes.
- A release affects multiple systems.
- The team needs a system-level risk review.
Instructions
- Review system boundaries, trust assumptions, and ownership lines.
- Review dependencies, runtime fit, and integration risk.
- Review deployability, observability, and recovery paths.
- Return prioritized system-level findings.
Constraints
- Focus on system behavior, not code style.
- Keep findings concrete and actionable.
- Separate blockers from watch items.
Output Format
- architecture review
- prioritized risks
- recommended changes
- deployment or rollout concerns
Examples
- "Review this service architecture before we build it."
- "Is this multi-runtime design safe to ship?"