030-architecture-adr-general

ADR Drafting helps teams document significant architectural decisions by creating new Architecture Decision Record files with a standard structure. It inspects your repository for existing ADR conventions, then drafts a new record with Title, Status, Context, Decision, and Consequences sections—defaulting to `docs/architecture/adr` when no convention exists.

Create and maintain architecture decision records (ADRs) using established conventions, templates, and a built-in validator. The skill guides you through prospective and retrospective record creation, enforces quality standards like one decision per record and credible alternatives, and helps manage decision lifecycles with status tracking and supersession links. Use it to build a durable, reviewable record of why architecturally significant choices were made.

Create ADRs that capture the reasoning behind significant technical choices, including context, alternatives considered, and trade-offs. The skill guides you through gathering implementation details, identifying decision drivers, and structuring records that help future developers understand why architectural choices were made.

This skill guides you through authoring Architecture Decision Records (ADRs) that capture major technical choices with full context. It validates decisions against existing architectural stances, engine compatibility, and GDD requirements, then generates a structured record with status, dependencies, and consequences tracked. Use it to retrofit missing sections into existing ADRs or create new ones from scratch.

This skill generates Architecture Decision Records (ADRs) that capture the context, decision, and consequences of significant technical choices. It guides you through gathering essential information, selecting from three formats (MADR, Nygard, or Y-Statement), and produces a structured document that preserves reasoning for future engineers.

The ADR skill helps you record major architectural choices in a structured format that captures the reasoning behind decisions, not just the outcome. It stores numbered records in your project's docs folder and guides you through context, trade-offs, and consequences so your team can understand why decisions were made.