← Skill Library
Operating System

Chief of Staff Agent System

A dispatcher and specialist-agent organization on top of an enabled GTM Brain. The CoS routes, verifies, and reports. Specialists do the domain work.

This layer assumes a GTM Brain is already the shared working-context folder.GTM Brain →

The Stack

  • Harnesses
    Cursor
    Codex
    Claude
  • Prerequisite
    GTM Brain
    AGENTS.md
  • Live systems
    Email
    Calendar
    Upside GTM data
  • Optional share
    Notion

Start with the right mental model

HUMAN CONTROLPrincipalGoals · prioritiesApprovalsAccountability stays hereCOORDINATIONChief of StaffRoute · verify · reportStay availableNot a generalist executorSPECIALIST EXECUTIONDomain ownersRevenue · Finance · CRMSecurity · EngineeringNarrow charters, clear toolsREADSGTM BrainShared context.Not rebuilt here.
Coordination, not executionIf a specialist owns CRM configuration or security review, the CoS routes there instead of acting directly. Responsibility stays legible.

Give the CoS a narrow mandate

Does

Triage the outcome, route to the owner, create a bounded task when no role fits, verify the artifact, and report what was inspected — plus the gaps that still need a human.

Does not

Silently perform specialist work, approve its own high-impact actions, override a safety policy, or treat a status label as proof that the requested artifact exists.

Design roles around decisions, not tools

RoleOwnsDoes not own
Chief of StaffTriage, routing, verification, synthesisSubstantive specialist execution
RevenuePipeline strategy, qualification, account researchCRM schema and permission changes
CustomerHealth, renewals, support signals, retentionContract interpretation and product implementation
FinanceCash, forecasting, budgets, accounting analysisLegal interpretation and people-policy decisions
CRM adminRecords, schema, validation, safe data operationsRevenue strategy or platform administration
SecurityRisk, controls, technical reviewsDevice admin, legal advice, application fixes
EngineeringCode, integrations, infrastructure, testingAgent-platform config and business-policy approval
Platform ownerTasks, skills, connectors, permissions, schedulesBusiness-domain execution

Make the handoff a complete work packet

Handoff

Desired outcome, exact target and context, permission boundary, acceptance criteria, prior decisions and open gaps. The specialist should be able to work without inventing business intent.

Completion report

Outcome, evidence, exact changes, exceptions, open gaps. This is what the CoS verifies. A dispatch acknowledgment is not evidence of completion.

Dispatch, then verify

1ReceiveDesired outcome2RouteOwner of the domain3Stay openHuman can still ask4InspectArtifact or live result5ReportOnly what was verified
Dispatched / in progressThe task was handed off, or an agent is working. Neither proves the requested artifact exists.
Verified completeThe outcome was inspected: a cited deliverable, a live setting read back, a record re-read, a test that passed. Report only that.

Define approval boundaries before connecting tools

Action classDefault policyTypical requirement
Read-only researchAllowed within role scopeRecord sources and coverage gaps
Internal draftingAllowedLabel assumptions and keep a review step
External communicationHuman approval or bounded authorityVerify destination and content immediately before send
Financially scaled activityApproval requiredState per-run and recurring cost first
Credentials or security settingsControlled changeLeast privilege, backup, change review, readback
Destructive operationsExplicit itemized confirmationConfirm exact targets in the current interaction

How learnings move across the company

YOUR VAULTPrivate canonDream log · hard rulesfailure modes · skillsCustomers stay hereweeklySHARE JOBPortable-fact filterKeep operating rulesDrop names, numbers, peopleUnsure? Hold it back.publishNOTIONCompany CoS boardDated portable factsWhy it matters · vault pathReadable by every CoSpullOtherCoS agentsinto theirown inboxLearnings move. Canon does not fork. Private facts stay in the originating vault.

Share

Operating rules, failure modes and the protocol that now prevents them, skill patterns, source-guide gotchas, open questions another CoS might have answered.

Never share

Customer names, people, emails, pipeline amounts, forecasts, runway, credentials, internal IDs, deal strategy, raw notes. If you are unsure, hold it back.

Implement in stages

  1. Confirm the GTM Brain exists: shared working context, canon owner, source hierarchy, owned-memory areas.
  2. List recurring decisions and actions worth owning.
  3. Create a small role map: CoS, two or three specialists, one platform owner.
  4. Write charters: mission, exclusions, tools, safety boundary, memory, handoff targets.
  5. Initialize tasks with orientation-only startup turns.
  6. Adopt the handoff card for every substantive cross-agent request.
  7. Set the verification standard before connecting high-impact tools.
  8. Run a few real workflows. Automate only after the manual loop and its artifact contract are proven.