A command for recording project goals, decisions, options, observations, actions, outcomes, and revisited choices in a decision graph. A decision graph is a linked record of how a project evolves.

Use it to track feature goals, compare approaches, record implementation milestones, and revisit earlier decisions.

It preserves why important project choices were made, so later work can follow the reasoning instead of relying on memory.

How notactuallytreyanastasio/deciduous configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to notactuallytreyanastasio/deciduous. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/notactuallytreyanastasio/deciduous/main/.claude/commands/decision.md

Clone the repo

git clone --depth 1 https://github.com/notactuallytreyanastasio/deciduous

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/decision/github.svg)](https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/decision)

Your own site

<a href="https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/decision"><img src="https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/decision/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/decision"><img src="https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/decision.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,836 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.03836
Opus 5.5	$0.00004	$0.01534
Sonnet 5.5	$0.00002	$0.00767
Haiku 4.5	$0.00001	$0.00384

Measured 13d ago against content hash bbad5d2e0857, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

decision scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/decision.md · 316 lines

How it starts

The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Decision Graph Management

Log decisions IN REAL-TIME as you work, not retroactively.

When to Use This

You're doing this...	Log this type	Command
Starting a new feature	`goal` with -p	`/decision add goal "Add user auth" -p "user request"`
Choosing between approaches	`decision`	`/decision add decision "Choose auth method"`
Considering an option	`option`	`/decision add option "JWT tokens"`
About to write code	`action`	`/decision add action "Implementing JWT"`
Noticing something	`observation`	`/decision add obs "Found existing auth code"`
Finished something	`outcome`	`/decision add outcome "JWT working"`
Reconsidering a past decision	`revisit`	`/decision add revisit "Reconsidering auth"`

What NOT to Log - CRITICAL

The decision graph records the USER'S project decisions, not your internal process.

Do NOT create nodes for your own thinking, planning, reading, or tooling steps. Only log things the user would recognize as project milestones or decisions.

Skip these (meta/process noise):

"Reading codebase to understand structure"
"Planning implementation approach"
"Running tests to check status"
"Analyzing existing code"

Log these (user-visible project work):

"Add user authentication" (goal)
"Use JWT tokens" (option)
"Implemented JWT middleware" (action)
"JWT auth working, all tests pass" (outcome)

Quick Commands

Based on $ARGUMENTS:

View Commands

nodes or list -> deciduous nodes
edges -> deciduous edges
graph -> deciduous graph
commands -> deciduous commands

Create Nodes (with optional metadata)

add goal <title> -> deciduous add goal "<title>" -c 90
add decision <title> -> deciduous add decision "<title>" -c 75
add option <title> -> deciduous add option "<title>" -c 70
add action <title> -> deciduous add action "<title>" -c 85
add obs <title> -d <description> -> deciduous add observation "<title>" -c 80 -d "<description>"
- Observations MUST have both a title (short summary) and description (full detail)
add outcome <title> -> deciduous add outcome "<title>" -c 90
add revisit <title> -> deciduous add revisit "<title>" -c 75

Read the full file on GitHub · 316 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

13d ago Changed · -6 lines bbad5d2e0857
1mo ago Changed · +15 lines d5450553fade
1mo ago Changed · +1 lines 8425b12c5e4d
1mo ago Changed 0f5a5a8656c3
2mo ago Changed · -30 lines c3a8000a0f90
2mo ago First seen · 336 lines · 9 tokens per session scan A b83c3ba655fc

Subscribe to this mod's changes

decision is a command published in the GitHub repository notactuallytreyanastasio/deciduous (169 stars, last pushed 13d ago), licensed Apache-2.0. It adds 9 tokens to every session and 3,836 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

decision next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
decisionnotactuallytreyanastasio/deciduous	Command	169	13d ago	Apache-2.0	A	9	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

deciduous: Command for Claude Code