wa:design-adr

To create an architecture decision record, this Skill generates a structured document with Context, Decision, Rationale, Alternatives, and Consequences sections. It determines the next unique ADR number by inspecting existing local records to maintain consistent numbering continuity.

An architecture decision record formalizes technical decisions, such as choosing between SSR and CSR for a dashboard. It documents the context, trade-offs, and rejected alternatives to remove friction and ensure consistent architectural choices across a project.

You document software architecture alternatives by generating a structured record that explicitly captures Context, Decision, Rationale, Alternatives, and Consequences. This ensures all technical trade-offs and rejected options are consistently recorded for future project reference.

Yes, you can sync architecture decision records to Confluence. The workflow optionally checks Confluence to avoid numbering conflicts and can sync the finalized document after you complete the multistage Context, Drafting, and Review process.

No, this architecture documentation workflow requires no external dependencies. It reads project constants to determine the next ADR number and guides you through stage-aware status updates during the Context, Drafting, and Review process without needing additional packages.