Real-World Workflows
This is where deciduous gets interesting. Let's see how it works with Claude Code in practice.
The Core Insight
Manually running deciduous add commands is tedious. The real power of deciduous comes when Claude does the logging automatically as part of its normal workflow.
When you run deciduous init, it creates:
CLAUDE.md— Instructions telling Claude about the decision graph workflow.claude/commands/context.md— A/contextslash command for session recovery.claude/commands/decision.md— A/decisionslash command for graph management
This means Claude knows about deciduous and will use it.
Three Key Workflows
This chapter covers the three main workflows:
- The Claude Code Workflow — Claude logging decisions in real-time as it works
- Session Recovery — Using
/contextto recover state after compaction or new sessions - PR Documentation — Generating visualizations and writeups from the graph
The Key Rule
Log BEFORE you code, not after.
The decision graph captures what you're about to do and why, not what you did. This keeps the record accurate and captures the reasoning that would otherwise be lost.
This is the fundamental pattern:
# About to implement something $ deciduous add action "Implementing rate limiter" -c 85 # ... do the implementation ... # Record the outcome $ deciduous add outcome "Rate limiter working" -c 95 --commit HEAD
Let's see this in practice.