All shelves / Mods / Workflow
chief-of-staff
By pwsaragossy
chief-of-staff is a Claude Code workflow mod by pwsaragossy.
Draws a Projects pane of each project's status and next action and a Threads pane, and refuses a thread brief that names no specialist.
DrawsHolds a command
Install
The marketplace name is chief-of-staff.
claude plugin marketplace add pwsaragossy/chief-of-staff claude plugin install chief-of-staff@chief-of-staff
It runs inside the Claude Code process. The side panel is only what the author's README names. Read the repo before you install, or run claude plugin validate on the plugin folder.
- Version
- 0.10.1
- License
- Apache-2.0
- Repo stars
- 5
- Last change
- 2026-11-08
What it can reach
- Draws in the session
- Holds a command
- Reaches the network or an outside service
- Calls another program on this machine
Open Claude Code in any folder and run /chief-of-staff:setup, which asks up to four questions: where the workspace goes, where the company library goes, whether to back up to private GitHub repositories, and whether to work with a team. Inside Claude Code, /plugin marketplace add pwsaragossy/chief-of-staff and /plugin install chief-of-staff@chief-of-staff do the same as the two install lines. Every hook does nothing outside a workspace, so the plugin does not affect your other projects. The local panel needs python3. Cloud sessions (Claude Code on the web) do not load plugins installed on your machine. The optional dispatcher that starts the next session on its own is off by default.
The marketplace, chief-of-staff, holds only this plugin. Briefing projects, threads, and specialists from one pane is why this page files it under workflow. command-center-bioinfo, for Claudelicious, one operator's Claude Code cookbook, draws a pane of the session's intent, running jobs, and open questions. saas-marketing-shalintripathi, for a pack of 90 B2B marketing agents, draws a board of the specialists routed, each deliverable as it lands, and the facts left for you to supply. This one is a small company of agents for one owner or a team: a Projects pane with each project's status, next action, goal, memory, and chats, a Threads pane, a fixed playbook with tracks, nine specialist role cards with an independent reviewer, a company library of notes checked on every save, and a local panel. The pane module refuses a thread brief that names no specialist, and the plugin's command hooks stop a session that moves past a stage with an open item. A project can carry a deadline that the panel counts down.
Demo

What it hooks into
session.startWhen a session startscommand.runWhen you run its slash command/projects/threadsprompt.submitWhen you send a promptui.closeWhen its pane closestool.callAround a tool call, where it can hold oneturn.completeWhen a turn endsui.renderDraws into the sessionPaneToolUse
Read from the on() calls in its hook modules. Open its source under Files to check what each one does.
Slash commands 2
/projectsShow the workspace projects and open their chats/threadsMake this chat a project coordinator: work runs in threads, shown in the Threads pane
Hooks 7
SessionStart · startup|resume|clear|compactsh "${CLAUDE_PLUGIN_ROOT}/scripts/briefing.sh"UserPromptSubmitsh "${CLAUDE_PLUGIN_ROOT}/scripts/protocol.sh"PreToolUse · AskUserQuestionsh "${CLAUDE_PLUGIN_ROOT}/scripts/ask-guard.sh"PreToolUse · WebSearch|WebFetch|Agent|Write|Edit|MultiEdit|Bashsh "${CLAUDE_PLUGIN_ROOT}/scripts/protocol.sh"PostToolUse · Agent|WebSearch|WebFetch|Write|Edit|MultiEdit|Bash|Read|Grep|Globsh "${CLAUDE_PLUGIN_ROOT}/scripts/protocol.sh"Stopsh "${CLAUDE_PLUGIN_ROOT}/scripts/protocol.sh"SubagentStopsh "${CLAUDE_PLUGIN_ROOT}/scripts/protocol.sh"
Files
The author's README and source, 4 files. They load when you open them.
Facts
- Author
- pwsaragossy
- Category
- Workflow
- Marketplace
- chief-of-staff
- Version
- 0.10.1
- License
- Apache-2.0
- Repo stars
- 5
- Last change
- 2026-11-08
- Language
- Shell
- Files
- 61