Save Your Progress

The Problem

AI agents are stateless. Every conversation starts from zero. The agent doesn't remember what you decided yesterday, why you chose that architecture, what blockers you hit, or where you left off.

You end up re-explaining context, re-making decisions, and watching your AI partner repeat the same mistakes. I wrote about this in November--a pattern for maintaining context across sessions using Markdown files and slash commands^[1].

The Solution

Bonfire maintains a living context document that gets read at session start and updated at session end. Your AI partner picks up exactly where you left off. It's like a saved game for your work.

That's the core. No complex setup. No external services. Just Markdown files in your repo. It complements your issue tracker--use that for what needs to be done, use Bonfire for where you are and what you decided.

Beyond Start and End

The original pattern was two commands and a Markdown file^[2]. The plugin does more--but every addition addresses the same insight: the work has shifted from writing to directing.

Claude can write code for twenty minutes and often get it right. What's expensive is everything around it--building the wrong thing, missing edge cases, losing context, discovering misalignment after the code is written. The cost moved from typing to thinking.

These features are responses to that shift:

• Session state--preserve context so you don't re-explain
• Spec interviews--research the codebase, then surface ambiguity before it derails^[3]
• Work review--catch blindspots before they ship
• Subagents--isolate heavy operations so sessions last longer^[4]
• Proactive skills--read context automatically, suggest archiving when done

All feedback loops. All addressing where the bottleneck actually is now.

Save Your Progress

claude plugin marketplace add vieko/bonfire
claude plugin install bonfire@vieko