Manage Decisions

Name: Manage Decisions
Availability: InStock
Author: row0902

Document architectural decisions using standardized ADR templates and workflows.

Updated Jan 21, 2026

Search Tags:#documentation #adr #governance #traceability #software-engineering #team-workflows #architectural-decision

Ready to run

npx skills add https://github.com/Row0902/agents --skill manage-decisions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Manage Decisions
Source: https://github.com/Row0902/agents/tree/main/.agent/skills/manage_decisions
Command: npx skills add https://github.com/Row0902/agents --skill manage-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents and preserves the rationale behind architectural decisions to prevent knowledge loss and misguided rework.

Core Features & Use Cases

Standardized ADR templates to capture decision, context, consequences, and status.
Workflow guidance to create, review, and store ADRs in the repository for easy traceability.
Use Case: when considering a core library change or package restructuring, a formal ADR records the decision and rationale.

Quick Start

Draft a new ADR file in .agent/memory/ADR-00X-title.md following the standard ADR template.

Frequently Asked Questions about Manage Decisions

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

FAQPage Schema

How do I document architectural decisions to preserve rationale for future maintenance?▼

To document architectural decisions, draft a new ADR file in .agent/memory/ADR-00X-title.md. Use a standardized ADR template to capture decision, context, consequences, and status for future maintenance traceability.

What is an architectural decision record and when do I need one in software engineering?▼

An architectural decision record (ADR) is a formal document capturing decision rationale and context. You need an ADR when considering core library changes or package restructuring to prevent knowledge loss and misguided rework.

How do I create a repeatable workflow for reviewing and storing architectural decision records?▼

Create a repeatable ADR workflow by following guidance to create, review, and store ADRs directly in the repository. This ensures consistent architectural governance and easy traceability across team workflows.

Does this ADR template approach work for team workflows seeking architectural governance?▼

Yes, this ADR template approach works for team workflows seeking architectural governance by providing a formal template and repeatable process. It ensures consistent traceability of architectural decisions across software projects.

Why does my software project need formal ADR entries instead of standard documentation?▼

Your project needs formal ADR entries instead of standard documentation to specifically preserve the rationale behind architectural decisions. ADRs prevent knowledge loss and misguided rework by providing a structured, traceable decision history.