I’ve been using Claude Code every day for about a year, on several projects at a time: personal, work and hobby, some lasting weeks, others months or more. Out of that came a repo I now use every time I start a new project, and that I’ve also added to existing ones.
It’s a workflow for Claude Code. Every session starts from a short context that tells Claude:
what was done recently
what is being built right now
what you already decided, so it doesn’t get rediscovered (or “fixed”)
what tasks are in the queue
Old session notes get archived so they don’t eat the context. A lessons file collects the bugs, tool quirks and mistakes Claude keeps hitting from one session to the next, and every session loads it, so they stop coming back.
Two commands drive it: /session-start when you sit down, /handoff before you stop. Before trusting the notes, /session-start checks them against git, open PRs and running jobs, and tells you where they’re wrong.
It works for a single repo or a folder of several, on Linux, macOS and Windows.
If you struggle with work that spans many sessions, or with a big codebase, give it a try:
$ git clone
https://github.com/truongfelix/workflow.git
$ workflow/bin/adopt.sh ~/code/my-project
Then tell Claude: Set up the workflow: follow “Adopt in a new project” in /path/to/workflow/README.md
Happy to answer questions, and I’d really like to hear your feedback, especially whether it helped you or not.
submitted by
/u/Bill-Negative
Originally posted by u/Bill-Negative on r/ClaudeCode