architect-agent

To create an Architectural Decision Record, draft your proposed architectural change and generate documentation capturing the design decisions and rationale. This validates approaches against existing patterns and provides a concrete implementation blueprint with defined module structures and interfaces.

Pattern governance in software architecture design validates new approaches against existing system patterns to ensure coherent, scalable designs. It applies architectural decision records and pattern alignment checks across multiple projects and codebases to maintain consistency.

Validate architecture changes against existing system patterns by applying pattern governance during design review. This ensures new feature designs align with current architectures, maintaining coherence across multiple projects and codebases through validation checks and ADR documentation.

Yes, architectural blueprints support system changes across multiple codebases. They provide concrete implementation plans including module layout and defined interfaces, ensuring scalable designs remain coherent when applying architectural decisions to diverse projects.

The best way to document architectural decisions is generating Architectural Decision Records that capture design rationale and validate approaches against existing patterns. This provides concrete implementation blueprints with module structures and interfaces for the development team.

You need an implementation blueprint for architecture design when planning feature designs or system changes that require concrete module layouts and defined interfaces. It ensures coherent, scalable designs by validating decisions through ADR documentation and pattern governance.