chief-of-staff
Pursue a long-running goal in a single session by co-ordinating subagents.
- License 许可
- MIT
- 最近更新
- 2026-11-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- chief-of-staff
- description
- Pursue a long-running goal in a single session by co-ordinating subagents.
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml184 B
03 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.
Communication to and from subagents should be sparse. Communicate primarily through context pointers: research notes, previous commits, and others. Don't duplicate information already available via pointers.
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.
04 同仓库更多 Skills
workflow-launch-exec
Launch, orchestrate, and drive end-to-end multi-agent pipelines (BA -> DESIGN -> DEV -> VERIFY) for any task.
paseo-handoff
Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.
loop-me
Grill me about specs for the workflows I want to build, within this workspace.
loop-engineering
Use when the user wants Claude Code to keep working on its own until a goal is met — a self-running loop instead of write→wait→review→re-prompt. Helps decide if a loop is even worth building, picks manual vs automatic and open vs closed, distinguishes /goal vs /loop vs routines (/schedule), and wires up a CLOSED loop with a real verification gate (Stop hook running tests, or an LLM-judge + rubric when output isn't testable) plus a turn/budget ceiling so it never spins forever. Triggers on "loop", "döngü", "loop engineering", "auto mode", "run until tests pass", "self-running / autonomous agent", "/goal", "Stop hook", "ralph wiggum".
handoff
Compact the current conversation into a handoff document for another agent to pick up.
claude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.