architecture

You document architectural decisions by generating ADRs that capture context, alternatives, and consequences in a structured format. This skill analyzes your project requirements to evaluate trade-offs and drafts decision records that teams can revisit during design reviews.

An ADR is an architectural decision record that captures the rationale, constraints, and consequences of a design choice. You need ADRs when aligning teams on technology stack selections or evaluating patterns to prevent scattered documentation and brittle systems.

Evaluating architecture patterns for SaaS requires analyzing requirements and documenting trade-offs. This skill provides a structured framework to guide architecture sessions, validate tech choices, and capture constraints across MVP and enterprise contexts.

Yes, you can use this skill to align teams during design reviews by generating structured ADRs. It captures constraints, alternatives, and consequences, ensuring that architectural rationale is documented clearly for enterprise-scale project planning.

The best way to structure requirements analysis is to feed your project context into a framework that evaluates trade-offs and recommends patterns. This skill processes your requirements to draft ADRs, ensuring technology selections are validated against documented constraints.

Architectural decisions cause misalignment when rationale is not documented in a standardized format. Using ADR-driven decision records captures context, alternatives, and consequences in one place, preventing duplicated effort and brittle systems.