diff --git a/.changeset/chief-of-staff-shared-wiki-procedures.md b/.changeset/chief-of-staff-shared-wiki-procedures.md
index bfed6e9..d585a36 100644
--- a/.changeset/chief-of-staff-shared-wiki-procedures.md
+++ b/.changeset/chief-of-staff-shared-wiki-procedures.md
@@ -2,4 +2,4 @@
 "mattpocock-skills": patch
 ---
 
-`chief-of-staff` now looks for a shared wiki before starting its own. It also runs `retro` after every large subagent run and acts on the findings itself, and runs `to-spec`, `to-tickets` and `implement-spec` for large chunks of work, reading each skill by relative path so they can stay user-invoked.
+`chief-of-staff` now looks for a shared wiki before starting its own. It also runs `retro` on about one in five of its subagents' sessions, the ones where something went wrong first, and acts on the findings itself, and runs `to-spec`, `to-tickets` and `implement-spec` for large chunks of work, reading each skill by relative path so they can stay user-invoked.
diff --git a/skills/in-progress/chief-of-staff/SKILL.md b/skills/in-progress/chief-of-staff/SKILL.md
index 5aae533..22f0b66 100644
--- a/skills/in-progress/chief-of-staff/SKILL.md
+++ b/skills/in-progress/chief-of-staff/SKILL.md
@@ -50,7 +50,7 @@ The wiki is a historical record. It never claims to describe how things are now,
 
 Some procedures you run live in other skills, installed beside this one. To run one, read its `SKILL.md` at the path below, relative to this skill's directory, and follow it.
 
-- **Retro** (`../retro/SKILL.md`): every time you finish a run that dispatched many subagents (an `implement-spec` run, say), run a retro on those subagents' sessions. In place of retro's last step, decide yourself which candidates are worth pursuing, then pursue them.
+- **Retro** (`../retro/SKILL.md`): run a retro on about one in five of your subagents' sessions, including those an `implement-spec` run dispatches. Pick first the ones where something went wrong. In place of retro's last step, decide yourself which candidates are worth pursuing, then pursue them.
 - **Large chunks of work**: write a spec with `../to-spec/SKILL.md`, break it into tickets with `../to-tickets/SKILL.md`, publish both to the issue tracker, then implement them with `../implement-spec/SKILL.md`.
 
 ## Strategic View