decision-graph

Model design decision evolution from commit history using a deciduous DAG.

70|Updated Jan 12, 2026

Search Tags:#CLI #software-engineering #graph #commit-history #design-decisions #architecture-evolution #decision-graph

Ready to run

npx skills add https://github.com/gaearon/woodshed --skill decision-graph

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-graph
Source: https://github.com/gaearon/woodshed/tree/main/example/skills/decision-graph/original
Command: npx skills add https://github.com/gaearon/woodshed --skill decision-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Model the evolution of design decisions in a codebase. This skill helps teams document how architecture evolved over time by representing decisions, options, and outcomes as a traceable graph.

Core Features & Use Cases

Commit-driven design history: Build a deciduous DAG that records design decisions directly from repository history.
Narrative reconstruction: Surface the reasoning behind key changes, substitutions, and refactors to understand why certain paths were chosen.
Use Case: When refactoring a large codebase, use this skill to map decisions to commits and visualize how the design evolved.

Quick Start

Run deciduous commands in your repo to start constructing the graph from your commit history. For example: deciduous add goal "Capture design evolution" → deciduous add decision "Why this change?" → deciduous link ...

Frequently Asked Questions about decision-graph

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

FAQPage Schema

How do I track architecture evolution from commit history?▼

You can track architecture evolution from commit history by building a deciduous DAG that records design decisions, substitutions, and refactors directly from your repository commits.

Can I document design decisions as a graph during a codebase refactor?▼

Yes, you can document design decisions as a graph during a codebase refactor by creating and linking nodes that map decisions to commits, visualizing how the design evolved.

Do I need the deciduous CLI to capture design evolution?▼

Yes, you need the deciduous CLI to construct the narrative graph, using its commands to add goals, decisions, and links that relate nodes extracted from repository history.

What is a deciduous DAG for software design decisions?▼

A deciduous DAG for software design decisions is a directed acyclic graph that models how architecture evolves over time, surfacing the narrative reasoning behind key codebase changes.

When should I model design migrations as a decision graph?▼

You should model design migrations as a decision graph when your software project is undergoing architecture changes or refactors and needs a traceable record of why certain paths were chosen.

Is there a way to visualize the reasoning behind refactors from repository history?▼

Visualizing the reasoning behind refactors from repository history is achieved by running deciduous commands to construct a narrative graph that surfaces the outcomes and substitutions of key changes.