working-with-adr-tracking-projects

Create and manage Architecture Decision Records with standardized formats.

1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/MrHadiSatrio/Skills --skill working-with-adr-tracking-projects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: working-with-adr-tracking-projects
Source: https://github.com/MrHadiSatrio/Skills/tree/main/working-with-adr-tracking-projects
Command: npx skills add https://github.com/MrHadiSatrio/Skills --skill working-with-adr-tracking-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides conventions and guidance for managing Architecture Decision Records (ADRs) in software projects, ensuring clarity and consistency in architectural decision-making.

Core Features & Use Cases

  • ADRs as Constraints: Defines best practices for using ADRs as binding constraints in project development.
  • ADR Format: Standardizes the format of ADRs to maintain consistency across the project.
  • Creating New ADRs: Offers guidance on when and how to create new ADRs, including content structure and length guidelines.
  • Superseding and Deprecating: Explains the process for superseding or deprecating existing ADRs when necessary.
  • Planning: Assists in planning architectural changes by requiring ADR creation as a step in the implementation plan.
  • Use Case: When starting a new project or making significant architectural changes to an existing one, use this Skill to document decisions and maintain a clear record of the project's evolution.

Quick Start

To create a new ADR, run the command: adr create "My New ADR Title" --context "Description of the problem and context" --decision "The decision made" --consequences "The expected outcomes" --status "Proposed"

Frequently Asked Questions about working-with-adr-tracking-projects

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

FAQPage Schema
How do I document architecture decisions using ADRs in a software project?

Architecture Decision Records (ADRs) document architecture decisions by standardizing context, decision, and consequence fields. You can create an ADR by running a command with specific parameters to ensure project constraints are consistently recorded and traceable.

When should I create a new Architecture Decision Record?

You should create a new Architecture Decision Record when starting a new project or making significant architectural changes to an existing codebase. Creating an ADR should be a required step in your implementation plan to ensure architectural clarity.

How do I supersede or deprecate an existing ADR?

To supersede or deprecate an existing ADR, you follow the lifecycle management process defined by the project's ADR conventions. This ensures that outdated architectural decisions are properly marked while maintaining a clear historical record of the project's evolution.

What is the best way to standardize the ADR format across a project?

The best way to standardize the ADR format is to enforce a consistent structure for context, decision, consequences, and status fields. This ensures that all architecture decision records remain uniform and act as binding constraints throughout the development lifecycle.

Does managing ADRs require any specific dependencies or codebase environments?

Managing ADRs does not require external dependencies, as the process focuses on project-specific conventions and lifecycle management. It can be applied to any software project to govern the codebase through standardized architectural decision tracking.

Can I use ADRs as binding constraints for project development?

Yes, ADRs can be used as binding constraints for project development. By standardizing the creation and lifecycle of architecture decision records, the project ensures that all architectural changes adhere to documented decisions and maintain traceability.