ADR Assistant

Analyze existing ADRs and draft new ones with consistent structure and tradeoffs.

7|2|Updated Nov 9, 2025

Search Tags:#adr #technical documentation #architecture decisions #tradeoffs #engineering process #monorepo governance

Ready to run

npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill adr-assistant-prompt-or-die-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ADR Assistant
Source: https://github.com/Prompt-or-Die-Labs/hyper-forge/tree/main/.claude/plugins/core-dev/skills/adr-assistant
Command: npx skills add https://github.com/Prompt-or-Die-Labs/hyper-forge --skill adr-assistant-prompt-or-die-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ADR Assistant helps teams avoid unclear or inconsistent architectural decisions by guiding the creation and refinement of Architecture Decision Records with documented context, tradeoffs, and consequences.

Core Features & Use Cases

ADR Analysis: Reviews existing ADRs under ${WORKSPACE_DIR}/adr/, identifies related decisions, and flags conflicts or dependencies.
ADR Creation: Generates the next ADR number, follows the established ADR template structure, documents alternatives with tradeoffs, and includes an implementation timeline.
Template-Driven Documentation: Produces ADRs with consistent sections (Context, Decision, Alternatives Considered, Consequences, Implementation, References, Notes) to improve maintainability and discovery.

Quick Start

Ask the ADR Assistant to help you create an ADR for a new architectural decision and it will draft the next record following the project template.

Frequently Asked Questions about ADR Assistant

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

FAQPage Schema

How do I document architecture decisions and tradeoffs consistently?▼

To document architecture decisions consistently, use Architecture Decision Records to capture context, alternatives, consequences, and implementation details. This ensures architectural choices remain clear and maintainable throughout software development.

What is the best way to create an Architecture Decision Record for technology selection?▼

The best way to create an Architecture Decision Record for technology selection is to follow a template-driven approach that documents evaluated alternatives with tradeoffs, final decisions, and an implementation timeline.

How do I generate the next ADR number and follow an established template?▼

To generate the next ADR number, read existing Architecture Decision Records from your workspace directory, increment the sequence, and apply the established template to maintain structural consistency across records.

Can I analyze existing ADRs to identify conflicts or dependencies before making new architecture decisions?▼

Yes, you can analyze existing Architecture Decision Records to identify related decisions, flag conflicts, and surface dependencies. This review process prevents contradictory architectural choices during ongoing software development.

Does monorepo governance require documenting architecture decisions for each package?▼

Monorepo governance benefits from documenting architecture decisions for individual packages to maintain clear boundaries. Architecture Decision Records provide the necessary context, tradeoffs, and consequences for monorepo governance.

What sections should be included in an Architecture Decision Record?▼

An Architecture Decision Record should include Context, Decision, Alternatives Considered, Consequences, Implementation, References, and Notes sections. These sections improve maintainability and discovery of architectural decisions.