add-adr

Create Architecture Decision Records and update the project ADR index.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you capture and document structural decisions in your project, ensuring they are recorded and accessible for future reference.

Core Features & Use Cases

  • Create ADRs: Generate Architecture Decision Records for tech, pattern, tradeoff, or naming decisions.
  • Project Context Check: Verifies the presence of the groundrules structure and suggests necessary steps if missing.
  • Information Collection: Gathers the necessary details for the ADR, including title, status, and context.
  • Title Slugification: Converts the title into a filename-friendly format.
  • Generation: Outputs the ADR with the collected information, using a predefined template.
  • Index Update: Updates the ADR index in the project documentation.

Quick Start

Create a new ADR for your project using the 'add-adr' skill. The skill will guide you through the process of creating and documenting the decision.

Frequently Asked Questions about add-adr

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

FAQPage Schema
How do I document architecture decisions in a codebase?

To document architecture decisions, you create Architecture Decision Records (ADRs) that capture structural choices, context, and status, ensuring decisions remain accessible for future codebase maintenance.

What is an Architecture Decision Record and when should I create one?

An Architecture Decision Record (ADR) documents a structural decision in a project repository. You should create an ADR for tech, pattern, tradeoff, or naming decisions to maintain clear historical context.

How do I create an ADR for my project?

You create an ADR by executing the skill within your project directory to collect decision details, slugify the title into a filename, output the record using a template, and update the ADR documentation index.

Do I need a specific project structure to generate Architecture Decision Records?

Yes, generating Architecture Decision Records requires the groundrules structure to be present in your repository. The process checks for this structure and suggests necessary setup steps if it is missing.

Can I capture tradeoff and naming decisions in my project documentation?

Yes, you can capture tradeoff, naming, tech, and pattern decisions in your project documentation by generating structured ADRs that automatically update the project's decision index.