Verified:GitHub

wa:design-adr

Create Architecture Decision Records with context, rationale, alternatives, and consequences.

Updated Mar 26, 2026

Search Tags:#adr #software architecture #documentation automation #architecture decision record #decision documentation #confluence sync

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-adr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:design-adr
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/design-adr
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-design-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of documenting architectural choices by producing a complete, consistent Architecture Decision Record (ADR) with clear context, rationale, and alternatives.

Core Features & Use Cases

Structured ADR creation: Generates an ADR with Context, Decision, Rationale, Alternatives, Consequences, and References.
Numbering and continuity: Determines the next unique ADR number by inspecting existing local ADRs (and optionally checks Confluence to avoid conflicts).
Multistage workflow: Guides you through Context, Drafting, and Review with stage-aware status updates.
Use case: Use it when you need to formalize a technical decision such as choosing between SSR and CSR for a dashboard, including trade-offs and rejected alternatives.

Quick Start

Tell the Skill what decision to make by running /design-adr with your decision title or description.

Frequently Asked Questions about wa:design-adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create an architecture decision record with context and rationale?▼

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.

What is an architecture decision record used for in software engineering?▼

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.

How do I document software architecture alternatives and trade-offs?▼

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.

Can I sync architecture decision records to Confluence?▼

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.

Does this architecture documentation workflow require any dependencies?▼

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.