diff --git a/skills/implement/SKILL.md b/skills/implement/SKILL.md index 64a1ef1..cd1c0e3 100644 --- a/skills/implement/SKILL.md +++ b/skills/implement/SKILL.md @@ -114,21 +114,30 @@ orchestrator-agent. ### Step 3 — Boss merge step (on DONE or PARTIAL) -1. Open the per-iter journal file on the branch: - `git show iter/:docs/journals/-iter-.md` - (or check out the branch if a closer look is needed). -2. Accept the agent's Summary section as-is, OR rewrite it with - Boss-level framing. The rest of the journal file is factual and - preserved verbatim. -3. Append one line to `docs/journals/INDEX.md`: - `- YYYY-MM-DD — iter : -iter-.md` -4. Fast-forward main to the iter branch: +> **Switch to main FIRST.** The orchestrator-agent ends its run with +> the worktree on `iter/` (Phase 0 created the branch and +> all per-task commits land on it). Any Boss commit issued before +> `git switch main` lands on the iter branch by mistake — including +> the INDEX-append below. This is a recurring papercut. Do the +> switch before any Boss-side edit. + +1. Open the per-iter journal file on the branch (read-only, branch- + independent): `git show iter/:docs/journals/-iter-.md`. +2. Decide whether the agent's Summary section is acceptable or needs + a Boss-level rewrite. The rest of the journal file is factual and + preserved verbatim. Defer the actual edit to step 5 — it lands on + main, not on the iter branch. +3. Fast-forward main to the iter branch: `git switch main && git merge --ff-only iter/`. Since the iter branch was created from local `main` (Phase 0 of the orchestrator-agent) and no commits have landed on main since, the fast-forward is always linear. -5. Optionally delete the branch: `git branch -D iter/`. -6. If trigger is done-state and the user is away, write a +4. Append one line to `docs/journals/INDEX.md` and commit: + `- YYYY-MM-DD — iter : -iter-.md` +5. If the Summary needed rewriting (step 2), edit the journal file + on main now and commit. +6. Optionally delete the branch: `git branch -D iter/`. +7. If trigger is done-state and the user is away, write a `docs/WhatsNew.md` entry + `notify.sh` per CLAUDE.md's "Done-state notifications" subsection.