What problem does it solve?
This Skill eliminates the risk of outdated, incomplete architecture documentation that causes onboarding delays, repeated decision debates, and undetected architectural drift, ensuring all stakeholders have access to accurate, up-to-date system context.
Core Features & Use Cases
- Structured Arc42 Documentation: Generate lean core (6-section) or full 12-section Arc42 architecture docs tailored to project size, with templates for all standard sections including context, building blocks, runtime views, and deployment.
- Architecture Decision Records (ADRs): Capture significant architectural decisions with full context, rationale, and consequences to avoid relitigating past choices and preserve institutional memory.
- Fitness Functions & CI Integration: Enforce architecture rules (e.g., domain layer independence, no cyclic dependencies) via executable tests that run on every PR to prevent drift.
- Use Case: For a new event-driven e-commerce platform, use this Skill to draft the Arc42 lean core, document the decision to use Kafka for inter-service communication via an ADR, and set up ArchUnit tests to ensure domain classes remain framework-agnostic.
Quick Start
Use the software-architecture-documentation skill to create a lean core Arc42 document and ADR index for your new order processing microservice.
