Starting Over

Sometimes you want to wipe it and run the diagnostic fresh — a false start, a business that changed shape completely, or a first attempt you would rather not build on.

Back up your decision log first

A full reset restores tracked files to their template state, and decisions/log.md exists in the template. A reset overwrites it, and everything you have logged goes with it. There is no undo.

Before resetting anything, copy your decision log, your diagnostic record, and your context files somewhere outside the folder — or push to your private repository so the history survives in your commits.

The safer route: keep the record, redo the work

You usually do not need a full reset. Ask Claude Code:

Re-run the diagnostic from scratch. Archive my previous diagnostic and constraint rather than overwriting them.

You get a clean diagnostic, and last time’s reasoning stays readable. A previous diagnostic that turned out to be wrong is genuinely useful — it tells you how you were thinking about the business, which is often the more interesting data.

The full reset

Only after backing up:

git fetch upstream
git checkout upstream/main -- .

This restores everything tracked to the clean template state. Then run the deployment prompt again to rebuild from zero.

After a reset

You will go through both diagnostic phases again — soul and business. About 25 minutes.

Next

Command Reference