Browse / Software development / Teaching & study / workflow

workflow

truongfelix

A Claude Code workflow for long projects: short context, decisions remembered, lessons that stick across sessions

Open truongfelix/workflow → Checked against the four rules.

agentic-codingai-agentsanthropicbashclaudeclaude-codecontext-engineeringdeveloper-toolsworkflow

Built for Claude Code

ships .claude and nothing for other agents.

In its own words

README.mdtruongfelix/workflow

Every Claude Code session starts with an empty context. The usual fix is a notes file the agent updates at night and reads in the morning. It works until the notes are wrong: a branch "pushed" that never reached the remote, a job "still running" that died at 1 a.m., a to-do that shipped last week. The next session believes them.

This template checks the notes against the facts at every start. The handoff is a claim; the script is the fact.

  • **/session-start** reads git, GitHub and the machine (ground-truth.sh): each repo and branch against its remote,

open PRs and their CI, the items other sessions claimed, background jobs. Then the last handoff: it reports where they disagree, proposes the day's task, and waits for you.

  • **/handoff** runs the same script and records where things stand, for the next session on any machine.
  • **/board** shows the backlog, your decisions, the lessons and the handoffs as one page that updates itself.
  • **/autonomy** sets what Claude does without asking you: commit, push, open or merge a PR, release, …
  • **/checks** sets how the code is checked before a merge (its tests, GitHub CI, both) and the rules you keep.
  • **/trim** proposes what to keep, shorten or delete once your rulings and lessons grow.

What it looks like

Monday morning, /session-start on a project whose last session ended on Friday:

Quoting 41% of the README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.