Manage Decisions

Record and track software architecture decisions in a project repository.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill manage-decisions-carson-sweet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Manage Decisions
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/design-manage-decisions
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill manage-decisions-carson-sweet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented or lost project history by providing a structured, consistent way to document why specific technical or product decisions were made.

Core Features & Use Cases

  • Structured Decision Logging: Captures context, options, rationale, and consequences in a standardized format.
  • Traceability: Automatically links decisions to active work items and maintains a centralized project log.
  • Use Case: When a team debates whether to use a new database technology, this skill ensures the pros, cons, and final rationale are recorded for future developers to reference.

Quick Start

Ask the skill to record a new decision regarding the choice of authentication provider for the current project.

Frequently Asked Questions about Manage Decisions

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

FAQPage Schema
How do I track software architecture decisions in a project repository?

A decision log provides traceability by recording context, options, and rationale for technical choices. It solves the problem of fragmented project history by ensuring future developers can reference why specific product or technical decisions were made.

What's the best way to document the rationale for choosing a new database technology?

You can record a new decision by asking the skill to log the choice regarding your authentication provider or other technical selections. It appends markdown entries to the project decision log to maintain structured per-item documentation.

How does a centralized decision log maintain traceability for active work items?

Decision logging requires access to the project state directory and the ability to append markdown entries to the decision log. It is suited for software engineering teams needing structured project management and architecture documentation.

Do I need a specific project state directory to append markdown entries to a decision log?

Decision logging handles architecture and design decisions by capturing context, options, and consequences in a standardized format. It links these decisions to active work items to maintain a centralized project log for improved traceability.