dilim/skills
1
0 Fork 0
mirror of https://github.com/mattpocock/skills.git synced 2026-11-06 05:17:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

chief-of-staff: retro a one-in-five sample of subagent sessions

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Matt PocockandClaude Opus 5.5 committed 2026-10-31 13:46:50 +00:00
1 parent afbad9808c
commit a151256a0c
2 files changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

.changeset/chief-of-staff-shared-wiki-procedures.md
+1 -1
View File
@@ -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.
skills/in-progress/chief-of-staff/SKILL.md
+1 -1
View File
@@ -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