decision-graph
Use when building a deciduous decision graph to capture design evolution, architecture history, or how a codebase's design changed over time. Provides the deciduous CLI commands and graph structure guidelines.
npx skills add majiayu000/claude-skill-registry --skill original-1-5-gaearon-woodshed-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Decision Graph Construction You are building a **deciduous decision graph** - a DAG that captures the evolution of design decisions in a codebase. Use the `deciduous` CLI (at ~/.cargo/bin/deciduous) to build the graph. Run deciduous commands in the current directory (not inside the source repo). For git commands to explore commit history, use `git -C <repo-path>` to target the source repo. **CRITICAL: Only use information from the repository itself (commits, code, comments, tests). Do not use your prior knowledge about the project. Everything must be grounded in what you find in the repo.** ## Commit Exploration Use a layered strategy to find all relevant commits: **Layer 1: See all commits.** Start with the full list when building narratives. ```bash git log --oneline --after="..." --before="..." -- path/ ``` **Layer 2: Keyword expansion.** Once you have narratives, search for spelling variations and related terms you might have missed (e.g., "cache" → "caching", "cached", "LRU", "invalidate"). For each key identifier in your narratives, trace its full lifecycle: - Introduction - Changes and modifications - Renames - Deprecation or removal - Replacement by other mechanisms - Bec
- Commit Exploration
- DO NOT:
- DO:
- Finding the Story
- Narrative Tracking
- Hardening Phase
- Step 1: Extract concepts per narrative
- Step 2: Exhaustive search per concept
- Step 3: Rewrite narratives with gaps filled
- Cross-Narrative Connections
- Node Types
- CLI Commands
- Narrative Discipline
- Temporal Rule
git log --oneline --after="..." --before="..." -- path/ git log --all --after="..." --before="..." --grep="<concept>" --format="%H %s" -- path/ git show <sha> --format="%B" --no-patch Add nodes (returns node ID) deciduous add goal "Title of the goal" deciduous add decision "The question or choice point" deciduous add option "One possible approach" deciduous add observation "Something learned or discovered" deciduous add action "Descriptive title of what was done" deciduous add outcome "What resulted from the action"
What does the decision-graph skill do?
Use when building a deciduous decision graph to capture design evolution, architecture history, or how a codebase's design changed over time. Provides the deciduous CLI commands and graph structure guidelines.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill original-1-5-gaearon-woodshed-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.