chief-of-stafflisted

# Chief of Staff Structural maintenance for a roster v1 workspace. **Operate on the workspace itself**, not on the business workflows inside it. This skill scaffolds empty agent and function structure and audits completeness. Filling content into the scaffolds is a separate concern handled by function-level experts and role-level agents. When in doubt, defer to `conventions.md` in the workspace root for the canonical structure schema, and to `scripts/new-agent.sh` for the canonical scaffold contents (heredocs inside the script are the source of truth for every generated file). ## Working directory This skill operates from the workspace root only — the directory that contains `CLAUDE.md`, `conventions.md`, `config/project.yaml`, `roster/`, and the function dirs (`gtm/`, `product/`, etc.). If invoked from elsewhere, abort with: > Run chief-of-staff from your roster workspace root. ## How invocation works The user invokes via slash command or natural language. Parse intent into a plan name plus parameters. Examples: - `/chief-of-staff create-agent gtm sdr` → `plan=create-agent function=gtm agent=sdr` - `/chief-of-staff create-function design` → `plan=create-function function=design` - `/chief-of-staff audit-agent product/copy-agent` → `plan=audit-agent function=product agent=copy-agent` - `/chief-of-staff audit-repo` → `plan=audit-repo` When invoked without a plan, list the available plans and ask which to run. ### Out-of-scope intents v1 is a single workspace per dir