architecture-decision-record
Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.
npx skills add mohitagw15856/pm-claude-skills --skill architecture-decision-record --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Architecture Decision Record (ADR) Skill This skill produces a complete Architecture Decision Record (ADR) following the Nygard format — the most widely adopted standard. ADRs document the reasoning behind significant technical decisions so future team members understand not just *what* was decided, but *why*. ## Required Inputs Ask the user for these if not provided: - **ADR number** (sequential number in your ADR registry — e.g. 012; or "next available" if unknown) - **Decision title** (brief, e.g. "Use PostgreSQL as primary datastore") - **Context** (what situation led to this decision needing to be made?) - **Options considered** (at least 2; if only 1 is given, prompt for alternatives that were considered or ruled out) - **Decision made** (which option was chosen) - **Reason for choice** - **Status** (Proposed / Accepted / Deprecated / Superseded) - **Author and date** - **Team context** (optional — team size, relevant experience, org constraints; helps calibrate formality and depth of the Context section) ## Output Format --- # ADR-[NNN]: [Decision Title] **Date:** [YYYY-MM-DD] **Status:** [Proposed / Accepted / Deprecated / Superseded by ADR-NNN] **Author(s):** [Name(s)] *
- Required Inputs
- Output Format
- Context
- Options Considered
- Option [N]: [Name]
- Decision
- Consequences
- Positive Consequences
- Negative Consequences / Accepted Tradeoffs
- Risks
- Implementation Notes
- Review Date
- Deeper Materials
- Scoring Rubric (0–40)
What does the architecture-decision-record skill do?
Create an Architecture Decision Record (ADR) for any technical decision. Use when asked to document a technical decision, write an ADR, record an architecture choice, or capture why a technology or approach was selected. Produces a structured ADR with context, decision, consequences, and tradeoffs.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill architecture-decision-record --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.