Claude Plan Tracker hooks into Claude Code to automatically persist implementation plans and track which commits were made during each planning session.
The Problem
When working with Claude Code on complex features:
- Plans are stored in
~/.claude/plans/with random names likejazzy-booping-bentley.md - No connection between plans and git branches
- After context overflow or new session, you lose continuity
- No audit trail: which plan led to which commits?
How It Works
- Auto-load previous context — when you start a session, automatically inject the previous plan for your current branch
- Persist plans to your repo — plans are saved to
.claude/plans/{branch}.mdwhen sessions end - Track commits — know exactly which commits were made during each planning session
- Branch-aware — each git branch has its own plan history
Rewrite
Currently being rewritten from a TypeScript CLI tool to a native Go binary with zero runtime dependencies. Single static binary, no Node.js required.