Documents & Data · IN-DEPTH PROFILE

Create Architectural Decision Record Skill

Structured ADRs with context, consequences, rejected alternatives, and implementation notes.

Best for

Architecture teams documenting consequential technical choices

What you get

Gather required inputs + Write a standard ADR

Main limitation

A fixed template cannot ensure the decision evidence is complete or correct.

First risk

Unreviewed decision presented as settled. Generated ADRs default to Proposed and may contain inferred stakeholders or rationale. Require owner review before acceptance and verify the next sequence number before writing.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-24

Pinned revision · 1f564408

Open pinned commit ↗
SkillSignal profileEditorial metadata

Updated 2026-09-24

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Create Architectural Decision Record is a GitHub Awesome Copilot template for durable architecture decisions. It captures context, the chosen decision, positive and negative consequences, rejected alternatives, implementation notes, stakeholders, and references in a predictable Markdown structure.

This is aimed at Architecture teams documenting consequential technical choices. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Gather required inputsConfirm context, decision, alternatives, and stakeholders.
  • Write a standard ADRGenerate numbered front matter and coded consequence sections.
  • Preserve rejected optionsDocument why alternatives were not selected and what may change later.
What makes it different
  • Produces predictable, machine-readable decision records.
  • Requires both benefits and trade-offs instead of documenting only the winning option.
Community signalNo attributed third-party rating yet

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add github/awesome-copilot --skill create-architectural-decision-record --agent github-copilot
Personal install
npx skills add github/awesome-copilot --skill create-architectural-decision-record --agent github-copilot -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.agents/skills/create-architectural-decision-record/
Personal path~/.copilot/skills/create-architectural-decision-record/
Official agent docs

Copilot also accepts .github/skills and .claude/skills at project scope. Preview untrusted Skills before enabling scripts.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Gather required inputs

Confirm context, decision, alternatives, and stakeholders.

02

Write a standard ADR

Generate numbered front matter and coded consequence sections.

03

Preserve rejected options

Document why alternatives were not selected and what may change later.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Produces predictable, machine-readable decision records.
  2. Requires both benefits and trade-offs instead of documenting only the winning option.

Limitations

  1. A fixed template cannot ensure the decision evidence is complete or correct.
  2. The workflow writes Proposed ADRs but does not manage approval, supersession, or governance.

BEST FIT

Who it is for

→

Architecture teams documenting consequential technical choices

→

Repositories that need searchable decision history

BEFORE YOU USE IT

Risks to review before use

Medium

Unreviewed decision presented as settled

Generated ADRs default to Proposed and may contain inferred stakeholders or rationale. Require owner review before acceptance and verify the next sequence number before writing.

SECURITY

What the permission profile means

  • Avoid embedding credentials, private architecture diagrams, or exploitable details in broadly shared ADRs.
  • Use repository review and ownership rules before changing status to Accepted.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Create Architectural Decision Record Skill FAQ

What is the Create Architectural Decision Record Skill?

Structured ADRs with context, consequences, rejected alternatives, and implementation notes. Create Architectural Decision Record is a GitHub Awesome Copilot template for durable architecture decisions. It captures context, the chosen decision, positive and negative consequences, rejected alternatives, implementation notes, stakeholders, and references in a predictable Markdown structure.

How do I install the Create Architectural Decision Record Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the pinned commit and read the current SKILL.md.

Is the Create Architectural Decision Record Skill safe to use?

SkillSignal checked the source on 2026-09-24, but that is not a runtime test or security certification. Review the “Unreviewed decision presented as settled” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked

TAGS

adrarchitecturedocumentation

Original SkillSignal editorial profile grounded in GitHub Awesome Copilot commit d7e4ad98, checked 2026-09-23; not independently executed or security-certified.