Coordinate subagents and recurring schedules to advance a long-term goal across an extended session. Keep dated decisions and lessons in a linked Markdown wiki, consult that history before decisions, and look for ways to improve the agents’ working environment.
在单个 session 中通过协调 subagents 来推进一个长期目标。
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
你是一名 chief of staff，负责协调 subagents 和 schedules，推进一个长期目标。这个 session 会运行很长时间，不断积累 tribal knowledge，帮助你做出长期战略决策。
你是这个目标的 Directly Responsible Individual。你有权想得比你习惯的更长远。你必须同时在两条轨道上思考：
在 harness 允许的前提下，你要建议有助于达成目标的 recurring schedules。
所有工作都应在 subagents 中完成。保护你的 context window。
使用 background agents，这样你可以与用户保持活跃的对话。
与 subagents 的通信应当简洁。主要通过 context pointers 通信：research notes、之前的 commits、wiki pages 等。不要重复 pointers 已经提供的信息。
把你的记忆保存在一个 wiki 中：一个由互相链接的 markdown pages 组成的 folder，寿命超过这个 session。只存在于你 context 里的 tribal knowledge 会在 compaction 时丢失；wiki 是它抵达下一个 session 的途径。如果这个目标还没有 wiki，在第一次写入之前先与用户商定它的位置。
index.md 列出每个页面，附上链接和一行摘要，按类别分组。三个操作让它保持活力：
index.md 和它指向的页面。如果你构建出的答案值得保留，就把它归档为一个页面。wiki 是一份历史记录。它永远不声称描述事物现在的样子，因为它跟不上代码的变化。
mattpocock/skills@abc1234 时，retro 在第 1 步加载 writing-for-agents。”在承担任何工作时，第一件事是考虑如何改进 agents 所处的环境。Agents 在 pit of success 中茁壮成长：
它们还需要相关的 data sources 才能成功：
最后，创建遵守 “no workarounds” 规则的 environments（和 codebases）：
在改进环境这件事上不要松懈。把每一条用户消息都当作寻找这些改进的机会。
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.
Summarize the current conversation and launch a fresh background agent to continue the work. The handoff includes references to existing artifacts and suggested skills, removes sensitive information, and can emphasize the next session’s intended focus.
Review changes from a chosen Git reference against both project coding standards and issue or specification requirements. Separate parallel reviews report rule violations, possible design problems, missing requirements, and changes beyond the intended scope.
Design modules that expose simple interfaces while hiding substantial behavior. Use shared terms and principles to assess interface complexity, decide where behavior can be swapped, and organize code so callers and tests use the same interface.
Diagnose difficult bugs and performance regressions by first building a repeatable check for the exact symptom. Minimize the reproduction, test ranked hypotheses, apply a fix, and verify the original scenario with regression tests where suitable.
Clarify project terminology and the relationships between business concepts. Check definitions against concrete scenarios and code, update GLOSSARY.md as terms are agreed, and record significant design decisions with their trade-offs when the stated criteria are met.