Coding
Architecture review before implementation
Review an implementation plan against existing architecture, service boundaries, data contracts, performance constraints, and migration safety before code starts.
[ workflow / coding ]
Architecture review before implementation
Before an agent or engineer starts coding, Cosmos performs a design gate. It reads the proposed plan, maps the affected services and contracts, checks architecture rules and historical incidents, flags risky migrations or API changes, and either approves implementation or returns required plan changes.
07 nodes
05 edges
Ticket / RFC status changed
RFC · ADRs · owners · prior incidents
Services · APIs · data contracts
Migration · perf · privacy · rollback
Decision
Safe to implement?
Tech lead review required
Decision
Safe to implement?
Tech lead review required
Guardrails added to ticket
Workflow prompt
Paste this into Augment to reproduce the workflow end-to-end.
Cosmos, when a ticket or RFC is marked ready for implementation, run an architecture review before any code is generated. Read the implementation plan, linked RFC or ADR, affected codeowners, service boundaries, schemas, public APIs, feature flags, and prior incidents in the same area. Check for boundary violations, duplicated platform primitives, backward-incompatible API changes, unsafe database migrations, missing observability, missing rollback path, and performance or privacy risks. If the plan is safe, approve it with implementation guardrails. If not, return required plan changes and block agent kickoff until the tech lead accepts the revised plan.