agentleFS
devdeepjsdevdeepjs/kobayashi-maru/.agents/skills/chief-of-staff/SKILL.md

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

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.
  • jddeliaSkill

    software-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

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
  1. Distinctive:

    All work should be done in subagents.

    line 20
  2. Distinctive:

    Use background agents so you can stay in active dialogue with the user.

    line 22
  3. Distinctive:

    Ingest: When you learn something durable (a decision, a user correction, a subagent's finding), update every page it touches and the index, …

    line 36
  4. Very specific:

    Query: Before a decision, read index.md and the pages it points to.

    line 37
  5. Very specific:

    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 …

    line 45
  6. Distinctive:

    Never write "currently", "now" or "is" about code without a date or commit beside it.

    line 46
  7. Distinctive:

    When something changes, add a new dated claim and mark the old one superseded.

    line 47
  8. Distinctive:

    No one-off workarounds, or hacks that bypass established processes

    line 65

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.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.
  • 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.md and 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, retro loads writing-for-agents in 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.