decision-registry

Record and retrieve architectural decisions in ADR or decisions.md files.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill decision-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-registry
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/decision-registry
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill decision-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents architectural “folklore” by recording why major choices were made, keeping alternatives and trade-offs discoverable for future sessions and agents.

Core Features & Use Cases

  • Register decisions with rationale: add a decision with title, context, alternatives considered, justification, risks, and reversibility.
  • List and query decision history: retrieve prior decisions by searching decisions.md or the generated ADR files.
  • Supports ADR lifecycle and revocation: manages PROPOSED/ACCEPTED/DEPRECATED states and revokes by superseding with a new ADR.

Quick Start

Ask the skill to add an architectural decision by running: /anti-vibe-coding:decision-registry add "Decidi usar TanStack Query em vez de useEffect".

Frequently Asked Questions about decision-registry

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

FAQPage Schema
How do I record architectural decisions and preserve their rationale over time?

You can record architectural decisions by registering the title, context, alternatives, justification, and risks, which preserves the decision rationale in an ADR or decisions.md file for future project sessions.

What is the best way to track ADR status changes like accepting or deprecating decisions?

Tracking ADR status involves managing PROPOSED, ACCEPTED, and DEPRECATED states throughout the decision lifecycle, including revoking a prior architectural decision by superseding it with a newly generated ADR file.

How do I list and query past architectural decisions within a project?

You can list and query past architectural decisions by searching the stored records, retrieving prior technical choices, alternatives considered, and justifications from the generated ADR files or decisions.md.

Where are architectural decision records saved when using a decision registry?

Architectural decision records are saved to .claude/decisions.md or docs/design-docs/ADR-NNNN-*.md files, with the exact output location automatically detected based on your existing project layout.

Can I document trade-offs and reversibility for major technical choices across sessions?

Yes, you can document trade-offs and reversibility for major technical choices by registering the context and alternatives considered, ensuring the architectural justification remains discoverable for future sessions and agents.

Why does my project need architectural decision records instead of standard documentation?

Projects need architectural decision records to prevent architectural folklore, keeping the alternatives, trade-offs, and justifications behind major technical choices explicitly documented and discoverable over time.