arch-arc42-architect

To draft arc42 architecture documentation with embedded requirements, use a structured workflow that embeds REQ-* sections directly into architecture views and constraints. This ensures traceability from product requirements to ADRs and quality scenarios.

The best way to ensure traceability is embedding REQ-* sections directly into arc42 architecture documents. This links product requirements to specific ADRs, diagrams, and quality scenarios within a governance-ready review packet.

Generate a governance-ready review packet by drafting an arc42-style architecture document with embedded REQ sections, runtime views, and quality attributes. This packet links existing ADRs and guidelines to ensure validation against product requirements.

Yes, you can link existing ADRs and product briefs into arc42 architecture views. The documentation process connects these artifacts to context, building blocks, and cross-cutting concepts while maintaining requirement traceability.

Yes, you need an approved product brief and defined system scope to start drafting. Invoking the arc42 documentation workflow with these inputs generates a compliant architecture document with embedded requirements and linked ADRs.

Required sections for arc42-compliant architecture documentation include context, building blocks, runtime, deployment, and cross-cutting concepts. These sections embed REQ-* sections, quality attributes, and constraints to ensure full requirement traceability.