generate-adr

Generate Architecture Decision Records with a standard template.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill generate-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-adr
Source: https://github.com/vndkubi/bootstrap-toolkits/tree/main/.github/skills/generate-adr
Command: npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill generate-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions often lack consistent documentation and traceability, making it hard to understand why certain choices were made over time. This skill generates Architecture Decision Records (ADRs) using a standardized template to capture context, decision, alternatives considered, consequences, and status.

Core Features & Use Cases

  • Standard ADR templates ensure consistency across projects and teams.
  • Guided workflow from problem framing to documented decision, with references and status tracking.
  • Improves onboarding and future maintenance by preserving rationale behind technology choices.

Quick Start

Draft an ADR using the standard ADR template for your architectural decision.

Frequently Asked Questions about generate-adr

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

FAQPage Schema
What is an Architecture Decision Record and why do I need one?

Use a standardized ADR template to document technology choices, architecture patterns, and design alternatives. A complete ADR improves onboarding by capturing context, decision, alternatives considered, consequences, status, date, and references in a consistent format.

How do I write an Architecture Decision Record for a new technology choice?

Generate a complete Architecture Decision Record by applying a standard template across technology choices, architecture patterns, and design alternatives. The resulting ADR includes context, decision, alternatives considered, consequences, status, date, and references to ensure traceability.

What should be included in an Architecture Decision Record template?

A standard Architecture Decision Record template includes context, decision, alternatives considered, consequences, status, date, and references. Documenting these elements ensures consistent traceability for technology choices and architecture patterns across teams.

When should I document architecture patterns using an ADR?

Generate an Architecture Decision Record for any architectural decision requiring documentation, including architecture patterns and design alternatives. Documenting these choices ensures traceability and preserves the rationale behind technology decisions for future maintenance.

Does generating an ADR require any specific software engineering workflow tool?

Generating an ADR requires no external dependencies or specific workflow tools. It applies a standard template directly to your architectural decision, producing a complete decision record that fits your existing software engineering documentation workflow.