software-architect

To document architecture decisions with DDD alignment, create Architecture Decision Records in the /adr/ directory and Product Requirement Specifications in /requirements/. This ensures your strategic design choices are traceable and aligned with domain goals.

The best way to coordinate architecture decisions across teams is to maintain a living design doc with cross-team context using PRSs and ADRs. This approach captures product requirements and delegates work across roles while ensuring consistency.

To generate an Architecture Decision Record, initiate a design review for a specific service and ask the skill to draft the ADR. It provides structured outputs that capture key decisions, trade-off evaluations, and high-level system analysis.

You need to create Product Requirement Specifications during feature scoping and strategic design discussions. Capturing PRSs in the /requirements/ directory provides clear scope and acceptance criteria, supporting governance and traceability.

Yes, the approach supports inspecting existing ADRs to ensure consistency. You can request a review of any existing Architecture Decision Records in your /adr/ directory to verify that new features align with previous architectural decisions.

Relying on ADRs and PRSs for system design governance requires consistent maintenance of your /adr/ and /requirements/ directories. Without regular inspection and updates during architecture reviews, the living design doc can lose traceability and cross-team alignment.