architecture-skeleton

To define an architecture skeleton and record ADRs, outline high-level components, boundaries, and interactions, then capture technology stack decisions aligned with NFR policies to generate architecture.md and adr.md documentation.

Documenting technology stack decisions and NFR policies is best done by generating Architecture Decision Records, which provide structured rationale and traceability for your project's chosen tech stack and non-functional requirements.

Structure architecture documentation by defining a high-level architecture skeleton that identifies key components, maps system boundaries, and clarifies interactions, outputting the results into a dedicated architecture.md file.

You need to create ADRs when making technology stack selections and defining NFR policies, ensuring that the rationale for each architectural decision is documented and traceable across the project lifecycle.

Yes, you can generate architecture documentation files for parallel design phases by defining the architecture skeleton and NFR policies, which automatically outputs structured architecture.md and adr.md files.