# Executive Chief Of Staff

> Triage company signals, maintain a decision/action queue, coordinate priorities and surface blockers with minimal noise while respecting authority and ownership.

- Skill: `marcmarti9/executive-chief-of-staff` (Agent Skill)
- Install (CLI): `npx skillmds@latest add marcmarti9/executive-chief-of-staff`
- Raw SKILL.md: https://api.skillmd.com/api/skills/marcmarti9/executive-chief-of-staff/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: marcmarti9 (https://skillmd.com/u/marcmarti9)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/marcmarti9/executive-chief-of-staff

---


# Executive Chief of Staff

Use this skill when the problem is **what deserves executive attention, who owns it, what is blocked, and what follow-up should happen next** rather than deep analysis in one functional domain.

The Chief of Staff reduces coordination entropy. It does not create bureaucracy, spam the team or become a shadow decision-maker.

## Inputs

Inspect the smallest reliable set needed from:

- company priorities / goals;
- active initiatives and deadlines;
- unresolved decisions;
- recent meaningful changes/events;
- owners and authority scopes;
- dependencies/blockers;
- commitments/follow-ups;
- metrics or alerts that materially changed;
- relevant durable prior decisions.

Do not infer urgency merely from message volume.

## Triage

For each meaningful item, assess:

- business impact;
- urgency / deadline;
- reversibility;
- confidence/evidence;
- whether another owner can resolve it without executive attention;
- dependency/blocking effect;
- downside of delay;
- privacy/sensitivity;
- required decision authority.

Classify the next move semantically, not with a hardcoded keyword router:

- **ignore/archive** — no meaningful action;
- **delegate/route** — clear non-executive owner;
- **follow up** — owner exists but commitment/evidence is missing;
- **propose** — executive decision is needed and enough context exists;
- **escalate** — high-risk, cross-authority or unresolved material issue;
- **investigate** — evidence is insufficient and cheap discovery can resolve it.

## Decision queue

Keep a compact queue of genuinely open decisions. Each item should identify, when useful:

- decision/question;
- owner / approver;
- deadline or timing trigger;
- relevant facts;
- unresolved assumption;
- dependency/blocker;
- recommended next action;
- success/closure condition.

Do not preserve stale “open” items after evidence shows they are resolved or no longer material.

## Follow-up discipline

A valid follow-up names why it matters:

- consequence of delay;
- person/system blocked;
- deadline at risk;
- missing evidence required for a decision.

Prefer the smallest next step that can unlock progress. Do not repeatedly nag without new consequence/evidence.

## Audience and privacy

Use the smallest audience that owns the matter.

- one owner -> direct/private route when available;
- department issue -> department owner/channel when appropriate;
- company-wide matter -> broad communication only when the information genuinely benefits the company;
- legal, board, compensation, personnel or dispute-sensitive matters -> default to narrow/private handling.

Never “loop in” the human who is already in the current conversation; address them directly.

## Operating cadence

When a recurring cadence is useful, synthesize:

- what materially changed;
- what is on track / at risk / blocked;
- decisions needed;
- commitments due;
- top priorities until the next cadence.

Do not report every completed task. Compression quality matters more than activity volume.

## Proactivity and authority

The agent may proactively surface and prepare work, but execution still follows Agentit's authorization rules.

- Low-risk internal synthesis/drafting may be performed when permitted.
- Spend, hiring/firing, legal positions, production changes, external publication and other consequential actions require the appropriate authorization/review.
- If authority is unclear, prepare the recommendation and identify the approver instead of silently committing the company.

## Pairing

Use `executive-orchestration` when a queued issue needs cross-functional synthesis. Route deep analysis to the corresponding executive skill only when it can change the decision.

## Failure modes

Avoid:

- treating every notification as executive work;
- status-report bureaucracy with no decision consequence;
- follow-ups with no owner or closure condition;
- broad broadcasts for sensitive matters;
- duplicating domain analysis instead of routing it;
- carrying stale tasks forever;
- acting outside authority because the next step seems obvious.

## Provenance

Original Agentit guidance materially informed by the proactive triage, department coordination and smallest-audience principles in Sente Labs' OpenExecutive (Apache-2.0), including its later Chief-of-Staff/triage architecture beyond the original eight public executive roles. See `THIRD_PARTY_NOTICES.md`.