skills.rest
HomericIntelligence
HomericIntelligenceOFFICIAL
Explore all skills by this author →
GitHub

doc-generate-adr

Generate Architecture Decision Records with standardized templates and lifecycle statuses.

18|5|Updated Nov 3, 2025
Search Tags:#architecture#decision making#documentation#adr#record keeping#technical decisions
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill doc-generate-adr-homericintelligence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-generate-adr
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude/skills/doc-generate-adr
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill doc-generate-adr-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams systematically document significant architectural decisions, ensuring clarity, rationale, and future reference for technical choices.

Core Features & Use Cases

  • ADR Creation: Generates new Architecture Decision Records (ADRs) with a standardized template.
  • Decision Tracking: Provides a clear workflow for proposing, accepting, and managing ADRs.
  • Use Case: When your team decides to switch from one database technology to another, use this Skill to create an ADR documenting the context, the decision, the rationale, and the consequences.

Quick Start

Use the doc-generate-adr skill to create a new ADR for the decision "Adopted new CI/CD pipeline".

Frequently Asked Questions about doc-generate-adr

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

FAQPage Schema
How do I document architectural decisions for my project?▼

An Architecture Decision Record (ADR) documents significant technical decisions by recording context, the decision itself, rationale, alternatives considered, and consequences. This Skill generates standardized ADRs to track these choices systematically.

What is the best way to track the status of technical decisions over time?▼

Tracking technical decisions over time requires a lifecycle workflow with statuses like Proposed, Accepted, Deprecated, and Superseded. This Skill provides that workflow, allowing you to propose, accept, and manage ADRs as project architecture evolves.

How do I create a standardized template for recording technical decisions?▼

Creating a standardized template for technical decisions involves structuring the context, decision, rationale, consequences, and alternatives considered. This Skill generates ADRs with this exact structured format to ensure consistent documentation across your project.

When do I need to write an Architecture Decision Record?▼

You need an Architecture Decision Record when your team makes significant technical choices, such as switching database technologies or adopting a new CI/CD pipeline. ADRs document the rationale and consequences of these decisions for future reference.

Can I use ADRs to record alternatives and consequences for a database migration?▼

Yes, ADRs explicitly facilitate recording alternatives considered and consequences alongside the context and rationale for decisions like database migrations. This Skill generates records that capture all these structured elements for significant architectural changes.

Related Skills

Explore More Software Engineering Skills→
wesleyegbertowesleyegberto
3

architecture-decision-records

Document architectural decisions as structured ADR files under docs/adr.

Community
Advanced
tclemtclem
11

planning-multi-agent-projects

Create structured multi-phase project plans in repository markdown files.

Community
Advanced
nnexainnexai
1

gsd-check-todos

List and filter pending development tasks with roadmap correlation.

Community
Intermediate
ghalacticghalactic
2

adr-skill

Create, maintain, and review Architecture Decision Records in a repository.

Official
Intermediate