adr

Generate MADR-based Architecture Decision Records from active wiki pages.

5|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/cooperacode/forge --skill adr-cooperacode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr
Source: https://github.com/cooperacode/forge/tree/main/.forge/skills/adr
Command: npx skills add https://github.com/cooperacode/forge --skill adr-cooperacode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts architectural choices recorded in the active wiki into MADR-format Architecture Decision Records, providing traceability and a single source of truth for decisions.

Core Features & Use Cases

  • Detect explicit or implicit architectural decisions in the wiki and classify them as foundational (Theme/Initiative) or feature-scoped (Epic/Feature).
  • Generate per-decision ADR files following the template, including context, decision, alternatives, consequences, and sources.
  • Produce an ADR index, update artifact navigation, and register the ADR artifact in the work-item docs.

Quick Start

Instruct the system to scan the wiki, detect decisions, and generate MADR-format ADRs under artifacts/adr.

Frequently Asked Questions about adr

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

FAQPage Schema
How do I generate MADR Architecture Decision Records from existing wiki pages?

To generate MADR Architecture Decision Records, scan your active wiki to detect implicit and explicit architectural choices, then automatically write classified ADR files with context, alternatives, and citations to the artifacts/adr directory.

What is the best way to document architectural decisions scattered across a project wiki?

Documenting architectural decisions across a project wiki is best handled by extracting those scattered statements and converting them into structured MADR-format ADR files, providing a single source of truth with traceability and navigable indexing.

Can I use MADR ADRs to track both foundational and feature-scoped architectural decisions?

Yes, you can use MADR ADRs to track both foundational decisions classified as Theme or Initiative and feature-scoped decisions classified as Epic or Feature, ensuring all strategic and product-level choices are captured.

How are generated ADR files organized after extracting them from the wiki?

Generated ADR files are organized under the artifacts/adr directory, accompanied by an ADR index and updated artifact navigation to register the new ADR artifacts within the work-item documentation.

Do I need a specific wiki format to detect architectural decisions and create ADR artifacts?

You need an active wiki containing explicit or implicit architectural decision statements; the system reads these wiki pages to extract context, alternatives, and consequences for generating valid MADR documents.

Why convert wiki architectural choices into MADR format instead of leaving them in the wiki?

Converting wiki architectural choices into MADR format provides traceability and a single source of truth for decisions, preventing context loss by structuring context, alternatives, and consequences in standardized ADR files.