agentleFS
christofferbergjchristofferbergj/agent-skills/skills/agents/chief-of-staff/SKILL.md

chief-of-staff

Skill1 starsChanged 27 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, 18 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use claude-handoff, writing-beats and 5 more.

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

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 15 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 17 projects that use this

  • LesaniSkill

    writing-fragments

    Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.

    Also in 17 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 17 projects that use this

  • AnasX7Skill

    scaffold-exercises

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

    Also in 17 projects that use this

  • simo97Skill

    git-guardrails-claude-code

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

    Also in 17 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use /swarm for useful background delegates within available capacity.

    line 20
  2. Distinctive:

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

    line 22
  3. Distinctive:

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

    line 36
  4. Distinctive:

    Ingest: when a durable finding or correction arrives, update every page it touches and the index.

    line 37
  5. Very specific:

    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 …

    line 49
  6. Distinctive:

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

    line 67

“Common” is measured: kept by at least 6 in 10 of the 37 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

Use /swarm for useful background delegates within available capacity; retain coordination and bounded local work in the parent. Keep the user's goal and budget as the scope boundary.

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 memory

Keep durable goal knowledge in a wiki: interlinked Markdown pages that outlive this session. Look for a shared wiki first, one the user or other agents already keep, or the goal's existing notes location, 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, following project conventions within the authorized workspace.

  • index.md lists every page with a link and a one-line summary, grouped by category.
  • Each other page covers one decision, recurring problem, subsystem, or user preference, and links related pages.
  • Pages cite their sources (issues, PRs, transcripts, subagent reports) and canonical project documents; the sources themselves stay unedited, uncopied, and within their existing access boundary.

Three operations keep it alive:

  • Query: before a decision, read the index and the pages it points to. File an answer worth keeping as a page.
  • Ingest: when a durable finding or correction arrives, update every page it touches and the index.
  • Lint: at checkpoints, resolve contradictions, orphan pages, broken links, and claims overtaken by newer evidence. Suggest a recurring lint schedule only within the user's scheduling grant.

The wiki is a historical record; it describes when something was true, never how things are now. Date every claim. For code, cite the repository and commit where it was true, and write "currently", "now", or "is" about code only beside that date or commit. When evidence changes, add a dated claim and mark the previous one superseded.

Complete the memory checkpoint when durable findings have dated sources, code claims have commit citations, and the index reaches every page.

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:

  • 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

Propose evidence-backed environment improvements when they serve the goal. Prepare learning-driven instruction changes for review; a goal does not authorize unrelated environment work, recurring schedules, or external actions.

Complete each checkpoint when the goal predicate, delegated results, evidence, remaining work, and next decision are explicit. Stop or checkpoint at the agreed budget.

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.