A working copy of its own
/k0-work takes a story that has a plan and builds it in a git worktree under
.claude/worktrees/, on a branch named after the story, opened from the branch you are standing
on — not from main. You keep working in the repository; the Claude Code session works next
door, writing to the story's Log as it goes so a session that runs out of context hands over
cleanly. At the end its branch comes back as one merge commit and the copy is destroyed.
The folder is kept out of git's way through .git/info/exclude, never your .gitignore.
Why it stops where it stops
It will not open a worktree over uncommitted work, and says how much there is. Three things it never does, each of which has already cost somebody a day:
- It never pushes and never opens a pull request. Publishing is your decision.
- It never resolves a conflict. A program cannot tell a conflict it resolved correctly from one it resolved plausibly. A conflict stops everything and names the files.
- It never runs tests, a build or a dev server in there. A copied
.envcarries the base repository's port, and a test runner that finds a server already on it goes green against the old checkout. Tests run on your branch, after the merge.
How to use it
- Plan the story first: Plan on the note, or
/k0-plan K150. - Press Work, or type
/k0-work K150. - If the terminal closes, Resume picks the conversation up where it was.
- Once it has merged, run your tests on your branch, then
/k0-verify K150.
A whole epic, conducted
Next to Work sits a quieter word: Ultracode. On an epic, /k0-ultracode makes one session a
conductor that opens a window like this one for every story, merges them
one at a time and tells you which window needs you. On a single story it cuts the plan into
assignments for agents in copies of their own instead, then tests and counter-checks the result on
your branch. Either way it never pushes and never presses Done.
Small print
Merging commits whatever the session left pending, and a commit runs your hooks. k0 does not skip
them with --no-verify, so a pre-commit hook that runs the suite does run next door — and k0
says so.