doughnut: Skill for Claude Code

When the current conversation contains the execution being reviewed, also review the thread for process improvements and overlooked developer decisions. Do not implement findings, edit rules or skills, commit, push, or start plan execution.

The PLAN may have been removed by normal completed-plan cleanup. A partial capability name, surviving conversation context, old path, commit message, or distinct story phrase is sufficient input for discovery. Do not require the user to supply a deleted file's exact name.

The review is read-only except for amending the unfinished PLAN or creating a follow-up PLAN through slice-planning. Preserve existing working-tree changes when making those planning edits. Do not create a separate retrospective artifact unless the user asks.

1. Current conversation and execution transcript.
2. Current .planning/phases/ and .planning/quick/ contents.
3. Git history for renamed or deleted planning paths.
4. Commit messages and diffs containing distinctive story language.

Useful history operations include:

git log --all --name-status -- .planning/phases .planning/quick
git log --all --diff-filter=D --summary -- .planning/phases .planning/quick
git log --all --grep='<capability phrase>'
git log --all -S'<distinct story phrase>' -- .planning
git show <revision>:<historical-plan-path>

Recover the earliest execution-ready plan revision, its source seed/story when present, beneficiary, intended outcome, boundaries, and outside-in proof. Also record later plan changes that were explicitly approved or supported by new evidence; do not misclassify them as drift.

Determine completion from the latest PLAN's slice statuses and execution evidence, not the earliest revision or the file's presence alone. Any planned or in-progress slice means the plan is unfinished. Record completed slices and remaining work separately; a deleted PLAN requires history evidence of completion.

If two plans remain equally plausible after history inspection, stop and ask the developer to choose. Do not combine them.

• it updates the PLAN's slice status or cleanup;
• its message names the story, capability, or slice;
• its diff implements, proves, refactors, or documents the recovered story; or
• the execution thread explicitly associates it with the plan.

Record each included SHA and reason. Inspect intervening commits and exclude unrelated work; do not assume one contiguous range belongs to the plan.

Review all selected commit diffs together. When they are contiguous and contain no unrelated work, use the net diff from the parent of the first implementation commit through the last related commit. Otherwise review the selected patches together and inspect their changed files at the last related implementation commit. Do not let later commits or current uncommitted work contaminate the historical result, and never mutate the current worktree to reconstruct it. Keep planning-only changes as provenance, not as product-quality findings.