diff options
| author | Matt Pocock <mattpocockvoice@gmail.com> | 2026-10-31 13:47:43 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-10-31 13:47:43 +0000 |
| commit | 5ae481693d13b37d4d2c2c92d0b66d299c93e695 (patch) | |
| tree | e887a16139d0b4a49899f5c1c15987f76df6b91a | |
| parent | a496f5513d4a4cf889bc48e189e579f4b0bdf6aa (diff) | |
chief-of-staff: shared wiki first; retro and implement-spec as procedures (#1363)
* chief-of-staff: shared wiki first; retro and implement-spec as procedures
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chief-of-staff: procedure paths are relative to the skill directory
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chief-of-staff: retro every large subagent run and act on the findings
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chief-of-staff: retro a one-in-five sample of subagent sessions
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
| -rw-r--r-- | .changeset/chief-of-staff-shared-wiki-procedures.md | 5 | ||||
| -rw-r--r-- | skills/in-progress/chief-of-staff/SKILL.md | 9 |
2 files changed, 13 insertions, 1 deletions
diff --git a/.changeset/chief-of-staff-shared-wiki-procedures.md b/.changeset/chief-of-staff-shared-wiki-procedures.md new file mode 100644 index 0000000..d585a36 --- /dev/null +++ b/.changeset/chief-of-staff-shared-wiki-procedures.md @@ -0,0 +1,5 @@ +--- +"mattpocock-skills": patch +--- + +`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 8ea0f46..22f0b66 100644 --- a/skills/in-progress/chief-of-staff/SKILL.md +++ b/skills/in-progress/chief-of-staff/SKILL.md @@ -25,7 +25,7 @@ Communication to and from subagents should be sparse. Communicate primarily thro ## Wiki -Keep your memory in a **wiki**: a folder of interlinked markdown pages that outlives this session. Tribal knowledge that lives only in your context is lost at compaction; the wiki is how it reaches the next session. If the goal has no wiki yet, agree its location with the user before the first write. +Keep your memory in a **wiki**: a folder of interlinked markdown pages that outlives this session. Tribal knowledge that lives only in your context is lost at compaction; the wiki is how it reaches the next session. Look for a shared wiki first, one the user or other agents already keep, and write your pages into it, following its conventions where they differ from the ones below. Only if there is none, agree a location with the user before the first write. - `index.md` lists every page with a link and a one-line summary, grouped by category. - Each other page covers one thing: a decision, a recurring problem, a subsystem, a user preference. Link related pages to each other. @@ -46,6 +46,13 @@ The wiki is a historical record. It never claims to describe how things are now, - Never write "currently", "now" or "is" about code without a date or commit beside it. - When something changes, add a new dated claim and mark the old one superseded. Don't rewrite the old one. +## Procedures + +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`): 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 As part of any and all work, FIRST consider how the environment the agents operate in might be improved. Agents thrive in the **pit of success**: |
