25 October 2026
Chief of Staff في Claude Code: هدف واحد كبير وفريق subagents يشتغل عليهChief of Staff in Claude Code: One Big Goal and a Team of Subagents Working on It
Install a skill called Chief of Staff in Claude Code, give it a long goal, and it hands the work to background subagents and saves what it learns in a wiki for next time.
Who this guide is for
Claude Code users who want to run long work without the chat filling up
Key terms
- Subagent
- A small agent Claude starts for one job. It runs in the background and reports back, without crowding your main chat.
- Context window
- The space where Claude holds the conversation. The fuller it gets, the weaker its focus.
- Wiki
- A folder of linked markdown pages where Claude writes decisions and notes so they outlive the session.
The steps
Step 1
Open the skill page
The skill is by Matt Pocock, in the mattpocock/skills repo on GitHub, under skills, then in-progress, then chief-of-staff. It is still in progress and may change.
Read the file before installing it. It is instructions only, with no code that runs on its own.
Step 2
Install it in Claude Code
Personal skills in Claude Code live in ~/.claude/skills. Each skill has its own folder with a SKILL.md file inside.
Paste the command below into your terminal. It creates the folder and downloads the file.
PromptInstall commandmkdir -p ~/.claude/skills/chief-of-staff && curl -o ~/.claude/skills/chief-of-staff/SKILL.md https://raw.githubusercontent.com/mattpocock/skills/main/skills/in-progress/chief-of-staff/SKILL.md
Tip: For one project only, put it in .claude/skills inside that project folder.
Step 3
Run it yourself with your goal
The skill does not start on its own; you call it. Open Claude Code in your project folder and type the command with your goal.
Pick a long goal, not a small task: a product launch, or cleaning up a whole project.
PromptFirst command/chief-of-staff My goal: [the long goal]. First, split it into tasks and tell me which subagent gets which task.
Step 4
Agree on where the wiki lives
Before its first write, the skill has Claude agree the wiki location with you. It keeps an index.md listing every page, and each page covers one thing: a decision, a recurring problem or a preference of yours.
Every claim in it is dated, so you know when it was true.
PromptWiki locationKeep the wiki in [docs/wiki]. Whenever we decide something important or I correct you, write it there with the date.
Step 5
Follow it while it works
All the work goes to background subagents, so your chat stays light and you can keep talking to it. Ask for progress instead of waiting.
PromptProgress checkHow is the goal going? Tell me how many tasks are done, which one is running now, and whether anything needs my decision.
Step 6
Have it improve the setup for next time
The skill thinks on two tracks: how to finish the task now, and how to change the environment so the next task is easier. Ask for the second track directly.
PromptThe second trackNow that this task is done: what could I change in the project so the next task is easier? Suggest 3 changes, most important first.
Step 7
Schedule the reviews
If your tool allows schedules, the skill suggests recurring tasks, like a wiki review that looks for contradictions and orphan pages.
PromptWiki reviewReview the wiki: look for contradictions, pages with no links and anything that is out of date. Fix what you can and tell me the rest.
The takeaway
One big goal, a team working in the background, and a wiki that makes every run easier than the last.
Most value
Start building with me now
We sit together, break down your problem, and I build the AI solution with you step by step
- A private session with you
- Real building during the session
- Results you take with you when we finish
100% free
A free consultation about your problem
The full path
Access to every guide (49), starting from 29 AED
