chief-of-staff

作者: mattpocock

通过协调子代理,在单次会话中推进长期目标。

npx skills add https://github.com/mattpocock/skills --skill chief-of-staff

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

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

Be relentless in improving the environment. Use every user message as an excuse to search for these improvements.

来自 mattpocock 的更多技能

ask-matt
mattpocock
询问哪种技能
communicationresearchproductivity
claude-handoff
mattpocock
将当前对话移交给一个全新的后台代理,该代理会立即接手工作。
codebase-design
mattpocock
用于设计深度模块的共享词汇。当用户想要设计或改进模块接口、寻找深化机会、决定接缝位置、使代码更易测试或便于AI导航,或当其他技能需要深度模块词汇时使用。
designdevelopmentcode-review
code-review
mattpocock
审查自某个固定点(提交、分支、标签或合并基准)以来的变更,从两个维度进行——标准(代码是否遵循该仓库记录的编码标准?)和规范(代码是否符合原始问题/产品需求文档的要求?)。通过并行子代理运行两项审查,并并排报告结果。当用户希望审查某个分支、拉取请求、进行中的变更,或要求“从X开始审查”时使用。
testingdevelopmentcode-review
design-an-interface
mattpocock
使用并行子代理为一个模块生成多个截然不同的界面设计。当用户想要设计API、探索界面选项、比较模块形态或提到“设计两次”时使用。
developmentdesignapi
diagnosing-bugs
mattpocock
诊断循环,用于处理顽固错误和性能回归。当用户说“诊断/调试这个”,或报告某些东西损坏、抛出异常、失败或缓慢时使用。
testingdevelopmentcode-review
domain-modeling
mattpocock
构建并完善项目的领域模型。当用户希望确定领域术语或通用语言、记录架构决策,或其他技能需要维护领域模型时使用。
designdevelopmentdocument
edit-article
mattpocock
通过重组章节、提升清晰度及精简文笔来编辑和改进文章。适用于用户希望编辑、修订或优化文章草稿的场景。
documentcreative