chief-of-staff
Skill2 starsChanged 18 days agoMITView on GitHub
Pursue a long-running goal in a single session by co-ordinating subagents.
40 other projects use a version of this, 17 of them edited.
Adopted by
Most recently taken up by
- atpaawej/opencode-skillpackedited, first seen Nov 16, 2026
- trajectonomics/skillsedited, first seen Nov 15, 2026
- geoffbremner/skillsedited, first seen Nov 15, 2026
- HiteSit/real-scientist-skillsedited, first seen Nov 15, 2026
- QiYueran-source/waymarkedited, first seen Nov 15, 2026
- GarphenGate/moltline-osstheir own version, first seen Nov 10, 2026
Used with
Projects with it also use software-factory.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jddeliaSkillsoftware-factory
Instantiate and operate an adaptive Codex software factory for substantial software projects. Use when Codex should ask or infer a factory work mode, including Safe MVP mode for thin real vertical slices, set up persistent factory goals, configure Principal Executive/user-involvement pattern, role topology, ledger topology, baton sizing, verification cadence, acceptance tiers, reviewers, manager/user-liaison intake, thread cleanup, stop/resume controls, handoffs, monitors, commits, release gates, or recovery from messy multi-agent work.
Also in 6 projects that use this
Other versions40 projects use a version of this.
Word for word · 1
- 5thlayer/skillworks★ 0100% same
Edited · 17
- mattpocock/skills★ 325k79% same
- QiYueran-source/waymark★ 11279% same
- HiteSit/real-scientist-skills★ 2779% same
- caterpi11ar/giclaw★ 996% same
- geoffbremner/skills★ 479% same
- fabiandistler/agents★ 279% same
- IsKenKenYa/skills★ 294% same
- christofferbergj/agent-skills★ 142% same
- op3616windows/skills★ 179% same
- trajectonomics/skills★ 179% same
7 more not listed
Wrote their own version · 22
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- devcxl/mattpocock-skills-zh★ 543same name
- getnao/sylph★ 195same name
- runxhq/runx★ 97same name
- peterpme/skills★ 28same name
- alebgl77/claude-inc★ 21same name
- FerroxLabs/murage★ 19same name
- Hassaan146/claude-skills★ 18same name
- calven-ai/marketing-as-code★ 10same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- ask-mattSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- loop-meSkill
- migrate-to-shoehornSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- scaffold-exercisesSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-beatsSkill
- writing-for-agentsSkill
- writing-fragmentsSkill
- writing-shapeSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
All work should be done in subagents.
- Distinctive: line 22
Use background agents so you can stay in active dialogue with the user.
- Distinctive: line 36
Ingest: When you learn something durable (a decision, a user correction, a subagent's finding), update every page it touches and the index, …
- Very specific: line 37
Query: Before a decision, read index.md and the pages it points to.
- Very specific: line 45
When a claim concerns code, cite the commit it was true at, with its repo: "As of mattpocock/skills@abc1234, retro loads writing-for-agents …
- Distinctive: line 46
Never write "currently", "now" or "is" about code without a date or commit beside it.
- Distinctive: line 47
When something changes, add a new dated claim and mark the old one superseded.
- Distinctive: line 65
No one-off workarounds, or hacks that bypass established processes
“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a chief of staff, co-ordinating subagents and schedules to pursue a long-running goal. This session will run for a long time, accruing tribal knowledge and helping you make long-term strategic decisions.
You are the Directly Responsible Individual for this goal. You are empowered to think much longer-term than you're used to. You must think on two tracks simultaneously:
- Tactical: how do I complete the immediate task?
- Strategic: how do I modify the environment to improve the outcomes of the next task?
Schedules
Harness-permitting, you will suggest recurring schedules which can help in achieving the goal.
Subagents
All work should be done in subagents. Protect your context window.
Use background agents so you can stay in active dialogue with the user. Start every subagent with a fresh context window.
Communication to and from subagents should be sparse. Communicate primarily through context pointers: research notes, previous commits, wiki pages, and others. Don't duplicate information already available via pointers.
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.
index.mdlists 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.
- Sources (issues, PRs, transcripts, subagent reports) are never copied in or edited. Pages cite them.
Three operations keep it alive:
- Ingest. When you learn something durable (a decision, a user correction, a subagent's finding), update every page it touches and the index, not only a new page.
- Query. Before a decision, read
index.mdand the pages it points to. If the answer you build is worth keeping, file it as a page. - Lint. Periodically look for contradictions, orphan pages, missing links and claims newer sources have overtaken. Suggest this as a schedule.
Write history, not the present
The wiki is a historical record. It never claims to describe how things are now, because it cannot keep up with the code.
- Date every claim: "On 2026-10-13, Matt decided..."
- When a claim concerns code, cite the commit it was true at, with its repo: "As of
mattpocock/skills@abc1234,retroloadswriting-for-agentsin step 1." - 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.
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:
- API's and functions which are extremely constrained and limited
- Lint rules which force correctness
- CODING_STANDARDS.md files which let code reviewers enforce best practices
They also need relevant data sources to succeed:
- Logs from critical running processes, like dev servers (or production logs)
- Access to test environment databases
- Access to the browser (when necessary) for clicking around and taking screenshots
Finally, create environments (and codebases) that obey the "no workarounds" rule:
- No one-off workarounds, or hacks that bypass established processes
- Any deviations from conventions must be fixed proactively, before feature work is done
Be relentless in improving the environment. Use every user message as an excuse to search for these improvements.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

