Decision Tracking

Create AngularJS, create and manage ADRs with automated numbering and templates.

3|1|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/vanman2024/dev-lifecycle-marketplace --skill decision-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Decision Tracking
Source: https://github.com/vanman2024/dev-lifecycle-marketplace/tree/main/.archive/old-numbered-plugins/03-planning/skills/decision-tracking
Command: npx skills add https://github.com/vanman2024/dev-lifecycle-marketplace --skill decision-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Important architectural and technical decisions are often made without proper documentation, leading to lost context, repeated discussions, and difficulty onboarding new team members. This skill streamlines the process of tracking and documenting these decisions.

Core Features & Use Cases

  • Automated ADR Creation: Provides a script (create-adr.sh) to automatically create new Architecture Decision Records (ADRs) with proper numbering and a standard MADR template.
  • Next ADR Number Finder: Includes a script (find-next-adr-number.sh) to mechanically determine the next available ADR number, ensuring unique and sequential records.
  • ADR Index Management: Offers a script (update-adr-index.sh) to automatically update an ADR index (e.g., README.md) with all ADRs grouped by their status (Accepted, Proposed, Deprecated).
  • Standardized Templates: Provides templates and patterns for consistent decision logging and architectural documentation, promoting clarity.
  • Use Case: A tech lead needs to document a critical architectural decision, such as choosing a new database. This skill can automatically generate a new ADR with the correct numbering and a pre-filled template, then update the project's ADR index to reflect this new proposed decision.

Quick Start

Create a new ADR titled 'Use PostgreSQL for Database' in the 'docs/decisions' directory, then update the ADR index to reflect the new proposed decision.

Frequently Asked Questions about Decision Tracking

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

FAQPage Schema
How do I document architectural decisions in my project?

Document architectural decisions by creating Architecture Decision Records (ADRs) using standardized templates. ADRs capture the context, decision, and rationale for technical choices, ensuring team alignment and preserving reasoning for future reference.

What is an ADR and why should I use one?

An Architecture Decision Record (ADR) is a document that logs important technical choices with their context and consequences. ADRs prevent lost context, reduce repeated discussions, and help onboard new team members by maintaining a searchable decision history.

Can I automate ADR creation and numbering?

Yes. This skill provides shell scripts that automatically generate new ADRs with correct sequential numbering and pre-filled MADR templates, eliminating manual setup and ensuring consistency across your decision log.

How do I maintain an index of all my architectural decisions?

Use the ADR index management script to automatically update a central index grouped by decision status—Accepted, Proposed, Deprecated. This keeps your decision log organized and searchable as new ADRs are added.

What template format does this skill use for decision records?

This skill uses the MADR (Markdown Architecture Decision Records) template, a standardized format for documenting decisions with sections for status, context, decision, and consequences in plain text.

Do I need any dependencies or prerequisites to create ADRs?

No external dependencies are required. The skill uses executable shell scripts and works in any project directory. You only need a shell environment and a target directory for storing your decision records.