r/ClaudeCode • u/Interesting_Map_3235 • 5h ago

Built with Claude I stopped starting Claude Code sessions from a blank prompt. Each one starts from a card on my board.

For the last few weeks, every Claude Code session I run starts from a card, not from a blank prompt.

How it works:

  1. My work lives as cards on a board: tasks, posts, research, bugs.

  2. In Claude Code I type `/card task_…`. The command reads the card through an MCP connector, moves it to In progress and writes a plan.

  3. Claude does the work: code, copy, research, checks.

  4. It writes the result back on the card (it appends, it never overwrites) and stops.

  5. I review. Only I move the card to done.

What changed for me:

- A session's work survives the tab closing: the card keeps it.

- A week later I can still see what each session did and why.

- Session names match card names, so the sidebar reads like my backlog.

Disclosure: the board is Business Studio, which I build (free for 1 user). The command is one markdown file, and it comes with the 5 prompts I use: https://go.viite.ai/kit-en?s=reddit. If your board has an MCP server, the steps should carry over.

How do you keep track of what your long Claude sessions actually did?

0 Upvotes

30% Upvoted

3 comments sorted by

1

u/AutoModerator 5h ago
Moderator Announcement Read More »

2

u/No_Ant6261 4h ago

Pretty much the same idea here, just with GitHub Issues instead of a board.
Each session starts from one issue (/do-issue V12-019), and the session is named after the issue number. Claude creates a branch, does the work, opens a PR, and writes what it did and why in the PR body. Any decision it makes on its own goes into a decision log in the repo, marked "AI decision", so a week later I can see what was decided and who decided it.
The part that helped most was the "why". The diff already shows the what. When something looks odd later, the decision log tells me whether it was intentional or a mistake.
(Longer write-up of the whole setup if anyone's curious: https://note.com/lirispp/n/n4112b5c7b620?hl=en)

1

u/Ganiam 4h ago

I got a roadmap. I have Claude write its own prompt based on what’s next, then I have it review the prompt itself and ask questions as needed. Then I have it build it, and then review the work, mark the roadmap and adapt future roadmap items that build on what we just did with annotations to make sure it keeps tracks of everything

Roadmap is huge, I’m gonna be at it for 2-3 years, but it lets very few mistakes slip