skills.rest
mitul-bhatia
mitul-bhatiaCOMMUNITY
Explore all skills by this author →
GitHub

architecture-decision-records

Generate Architecture Decision Records in Michael Nygard's format under docs/adr.

Updated Apr 4, 2026
Search Tags:#architecture#documentation#adr#design-decision#coding-workflow
One-click install
npx skills add https://github.com/mitul-bhatia/Vibes --skill architecture-decision-records-mitul-bhatia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-decision-records
Source: https://github.com/mitul-bhatia/Vibes/tree/main/.github/skills/architecture-decision-records
Command: npx skills add https://github.com/mitul-bhatia/Vibes --skill architecture-decision-records-mitul-bhatia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often scattered across chat messages, PR comments, and memos. This skill records structured Architecture Decision Records (ADRs) in real time, so rationale, context, and trade-offs are preserved alongside the code.

Core Features & Use Cases

  • Structured ADR generation: captures decision title, context, alternatives, and consequences.
  • In-session documentation: auto-detects decision moments during coding and records them with timestamps.
  • Traceability: maintains an ADR log (e.g., docs/adr) for future reference and onboarding.

Quick Start

Record an architectural decision as an ADR with context and alternatives.

Frequently Asked Questions about architecture-decision-records

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

FAQPage Schema
How do I document architectural decisions during coding sessions?▼

Capture architectural decisions during coding by generating structured ADRs that record the decision title, context, alternatives, and consequences alongside your codebase.

What format do generated ADR documents follow?▼

Generated ADR documents follow Michael Nygard's format, structuring each record with a decision title, context, alternatives considered, and consequences to ensure rationale and trade-offs are preserved.

How do I store and reference architectural decision records in my project?▼

Store and reference architectural decision records by placing numbered ADR files under the docs/adr directory, creating a traceable log of design trade-offs for future reference and onboarding.

When should I record an architecture decision record?▼

Record an architecture decision record when teams discuss framework choices, system boundaries, or major design trade-offs during development and planning sessions to preserve context that would otherwise be scattered across chats and PR comments.

Can I update existing ADR documents as design decisions evolve?▼

Yes, you can update existing ADR documents as design decisions evolve. The skill supports reading, updating, and referencing ADRs to maintain an accurate log of architectural trade-offs throughout the project lifecycle.

Related Skills

Explore More Software Engineering Skills→
infantesromeroadrianinfantesromeroadrian

adr-new

Generate markdown Architecture Decision Records from a YAML template with sequential numbering.

Community
Intermediate
ZzulinZzulin
8

unity-perception

Generate structured Unity scene summaries and markdown dependency reports.

Community
Advanced
RazisafirRazisafir
1

implementing-secret-scanning-with-gitleaks

Implement Gitleaks secret scanning in git repositories with pre-commit hooks and CI/CD integration.

Community
Intermediate
JhabbigJhabbig

architecture-decision-records

Document architecture decisions with structured ADR records capturing context, options, and consequences.

Community
Intermediate