create-adrs

Generate retroactive MADR-style Architecture Decision Records from repository evidence.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/jrodrigopuca/skills --skill create-adrs-jrodrigopuca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-adrs
Source: https://github.com/jrodrigopuca/skills/tree/main/create-software-docs/sub-skills/create-adrs
Command: npx skills add https://github.com/jrodrigopuca/skills --skill create-adrs-jrodrigopuca

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Architecture Decision Records (ADRs) for significant technical decisions, ensuring that the rationale behind choices is captured and preserved, even retroactively.

Core Features & Use Cases

  • Retroactive ADR Generation: Creates ADRs for past decisions based on existing project context and evidence.
  • Evidence-Aware Rationale: Explicitly distinguishes between directly evidenced and reconstructed rationale.
  • MADR Structure Adherence: Follows the standard structure for ADRs, including context, decision, and outcome.
  • Use Case: After a major architectural shift, use this Skill to generate ADRs for the key decisions made months ago, using code and documentation as evidence to reconstruct the original reasoning.

Quick Start

Use the create-adrs skill to generate retroactive ADRs for the 'authentication-service' scope.

Frequently Asked Questions about create-adrs

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

FAQPage Schema
How do I generate architecture decision records for past technical decisions?

You generate retroactive architecture decision records by reconstructing context and rationale from existing repository evidence, explicitly marking uncertain information. This produces MADR-style documents for significant technical choices made previously.

What is a retroactive ADR and when do I need to create one?

A retroactive ADR documents the rationale behind a past architectural shift using existing repository evidence. You need to create one after a major technical decision has been implemented without initially recording its context, decision, and outcome.

How do I document technical debt and decision rationale using existing repository evidence?

You document technical debt and decision rationale by scanning repository evidence to reconstruct the original reasoning. The generated ADR explicitly distinguishes between directly evidenced facts and reconstructed rationale to maintain historical accuracy.

Can I update existing architecture decision records when new evidence is found?

Yes, you can manage existing architecture decision records by updating or preserving them based on new repository evidence. This ensures that reconstructed rationale and context remain accurate as the software project evolves.

Does the ADR generation process follow the MADR structure?

Yes, the ADR generation process strictly adheres to MADR-style structure. This standard format ensures every architecture decision record includes the necessary context, decision, and outcome sections for comprehensive technical documentation.