architecture-design

To create an architecture design document, use a guided template to draft system structure, technology choices, and deployment constraints, then save the final output to docs/architecture.md. This standardizes architecture documentation across new initiatives and feature redesigns.

The best way to align architecture design with PRD and functional design inputs is to use a centralized template that integrates these artifacts. This ensures your architecture documentation accurately reflects product requirements and functional specifications.

Yes, you should review existing architecture documentation if present in docs/architecture.md before generating a new design draft. This ensures your new system structure and technology decisions align with established project conventions.

A template-driven approach improves system structure documentation by enforcing a frontmatter-driven standard for outputting architecture files. This provides a structured, repeatable method that maintains consistency across different projects and feature redesigns.

Yes, you can use this architecture documentation template for both new products and feature redesigns. It guides teams in documenting system structure and technology decisions consistently regardless of whether the project is a new initiative or an update.

When using a frontmatter-driven template for architecture design, output is strictly guided to save as docs/architecture.md. This basic implementation focuses on structure and technology choices without adding custom formatting components or external dependencies.