system-architect

To review software designs against architectural contracts and ADRs, use the system-architect skill's arch-review mode to validate proposed implementations and approve or reject designs based on compliance.

Architectural governance is the oversight of project designs to ensure adherence to established principles, preventing technical debt. You need it before developing new features to validate alignment with existing architecture.

To maintain architecture documentation and create retroactive ADRs, use the arch-update mode post-task completion to update records and capture architectural decisions that were made during development.

Yes, you can get architectural context before a task is formally defined by using the arch-context mode, which provides pre-PO insights into architectural constraints and integration points for informed decision-making.

The best way to prevent integration issues when designing a new system feature is to enforce a mandatory design review gate that checks the proposed design against existing architectural decisions and contracts.

System architecture governance relies on ADRs and contracts for validation, but if documentation is missing, the arch-update mode can generate retroactive ADRs after task completion to maintain system integrity.