Chief of Staff Methodology
The Chief of Staff supports an accountable leader's capacity to operate across
domains. This skill helps prepare, triage, coordinate, surface trade-offs, and
preserve decision context; it does not transfer the leader's authority.
Solo operators and organizations
For a solo founder, the founder is the accountable decision-maker: prepare options,
trade-offs, an attention plan, and a review rhythm around their real decisions.
Do not invent a leadership team, delegated authority, or commitments. For an
organization, identify the executive sponsor and existing decision rights before
coordinating across teams. In both settings, prepare, coordinate, brief, and record;
the human decides and authorizes action.
An executive operating rhythm here connects pending decisions, evidence, and review
dates. Route meeting facilitation and records to meetings, organizational
structure and reporting lines to org-design, and repeatable business-process
ownership and handoffs to operational-design. Use an authorized task-system skill
only for confirmed commitments under the task-creation discipline below.
When to Load
Load this skill for executive-office work involving:
- Information triage, gatekeeping, escalation paths, or decision rights.
- Decision memos, executive briefing, board materials, or preparation for an accountable decision-maker.
- Calendar triage, meeting audits, strategic time, or attention allocation.
- Cross-functional coordination where ownership, dependencies, or escalation need clarification.
- Transparent organizational sensing or team-health concerns.
- Institutional memory, leadership transitions, documented decisions, or commitments.
- Chief of staff, CoS, executive operations, founder operations, decision support,
operating rhythm, or strategic attention that needs a bounded operating method.
When Not to Use
Do not use this skill for generic personal errands or covert employee surveillance.
For meeting facilitation use meetings; for organization structure use org-design;
for business operating processes use operational-design.
Do not use this skill as a meeting-transcript action-item generator or a general
backlog-capture mechanism. A recommendation, a discussion topic, or an inferred
next step belongs in a briefing or decision record unless an accountable owner
has confirmed a discrete commitment and a realistic due date. Use the authorized
task-system skill only after those conditions are satisfied.
What This Skill Provides
This skill provides six methodology domains as progressive disclosure through
references/. Load the reference matching the task using your agent's normal
means; no specific profile, memory, calendar, or orchestration system is assumed.
Reference Files
| Reference |
Load when |
File |
| Gatekeeping and triage |
Mapping information to authority, access, and escalation |
references/gatekeeping-and-triage.md |
| Executive briefing |
Preparing decision-ready material or an executive update |
references/executive-briefing.md |
| Leverage mechanisms |
Improving the leader's operating system without false measurement |
references/force-multiplication.md |
| Organizational sensing |
Addressing team-health or organizational signals responsibly |
references/organizational-sensing.md |
| Institutional memory |
Recording decisions, commitments, and authorized handoffs |
references/institutional-memory.md |
| Meeting and calendar triage |
Reviewing meetings and calendar choices with the leader |
references/meeting-and-calendar-triage.md |
| Source index |
Checking provenance and the limits of source treatment |
references/source-index.md |
Operating Method
- Identify the accountable human decision-maker, the decision rights already delegated, and the decision or outcome at stake.
- Gather authorized evidence and label it as verified fact, assumption, reported concern, or unknown. Do not invent costs, timelines, authority, or stakeholder views.
- Route ordinary work to its authorized owner. Keep direct, protected routes open for safety, ethics, legal, HR, fraud, retaliation, and whistleblowing concerns.
- Prepare options and trade-offs, then give a clearly labeled recommendation when the request calls for one. The accountable human reviews and decides.
- Record only decision-relevant material under the access, retention, correction, and handoff rules in the applicable reference.
Task Creation Discipline
Applicability: Only when creating or updating tasks in an authorized task system.
A task is a record of a concrete, documented commitment, not a place to store
advice, aspirations, meeting summaries, inferred next steps, or recurring
leadership habits. Create a task only when the source establishes all of the
following:
- A discrete outcome or next action that can be completed or explicitly reviewed.
- An accountable owner who has made, confirmed, or accepted the commitment.
- A realistic due date grounded in an explicit deadline, an agreed review date,
or context that supports a specific date. Never invent a date merely to fill
a required field.
- Enough provenance in the task or linked record for the owner to understand
the commitment and correct it.
Before creating the task, check all four conditions. If the source offers a
recommendation, a general principle, or an inferred action without an owner or
defensible due date, preserve it as a briefing observation or ask the accountable
human to confirm the commitment and date. Do not create the task.
When a task is created, include the owner and due date in the creation request,
then read it back and verify both fields persisted. If either is absent or wrong,
repair it before reporting success. A past deadline is a triage signal: surface
it as overdue for an explicit reschedule, completion, or closure decision rather
than silently assigning a new date.
Accountable Human Authority
This skill supports an accountable human leader. It may prepare, advise, triage,
synthesize, and surface trade-offs. It does not make employment, compensation,
disciplinary, legal, fiduciary, or other reserved decisions, and it does not
present an automated recommendation as a decision.
Name the decision-maker and applicable approval or review path in consequential
artifacts. A CoS function can coordinate delegated work, but it must route work
outside that delegation to the authorized owner. Human review is required before
material is issued as the leader's position.
Privacy, Confidentiality, and Ethics
Use only authorized, purpose-limited information. Prefer aggregate information
and the minimum data needed for the stated purpose. Be transparent about what is
collected, who can access it, how it is retained, and how people can correct it.
Do not use covert monitoring, individual trust scores, dossiers, gossip maps,
quiet-quitting labels, hidden relationship profiling, or speculative judgments
about people. Confidentiality has limits: safety, harassment, fraud, legal, and
policy obligations may require escalation through authorized channels. Preserve
anti-retaliation protections and involve qualified HR, legal, safety, or ethics
professionals for matters in their remit.
Boundaries
| Domain |
Boundary |
Use instead |
| Product definition and prioritization |
This skill prepares or coordinates a decision; it does not define product strategy |
product-methodology |
| Corporate or business strategy |
This skill structures a leader's operating work; it does not set strategy |
strategy-frameworks |
| Financial models and budgets |
This skill may surface a resource question but does not build or validate a model |
financial-modeling |
| Verification claims |
This skill prepares artifacts but does not turn missing evidence into a pass |
verification-methodology |
| Evidence presentation |
This skill does not prescribe a research-artifact hierarchy |
artifact-pyramids |
| Operational tooling |
It does not automate mail, calendars, personal data stores, or task systems |
Use the organization's authorized tools and policies |
Pitfalls
- Treating triage as a private veto instead of a transparent route to the authorized owner.
- Hiding uncertainty, weak evidence, or an unresolved conflict to make a brief look decisive.
- Speaking as the leader without review, approval, and clear authorship.
- Treating people signals as proof of individual performance, intent, or protected-status issues.
- Storing personal impressions instead of durable, documented decision context.
Related Skills
artifact-pyramids for layered, inspectable decision artifacts.
financial-modeling for assumptions-led financial analysis.
product-methodology for product decisions and prioritization.
strategy-frameworks for strategy choices and trade-offs.
verification-methodology for evidence-backed completion claims.
slack — channel triage and message search through the Slack Web API; confirmed posting only. The everyday read layer for "what was said, find it later."
notion — knowledge search, page and database reads through the Notion API; confirmed edits only.
email — transactional email sends and delivery verification (bounces, spam reports, event-webhook signature check) through SendGrid. Read-only discovery before any send.
Completion
Complete when the requested brief, triage recommendation, attention plan, or decision
record identifies the human decision owner, evidence gaps, and next review or
escalation. Stop at missing authority or unavailable evidence; record the gap rather
than claiming a decision or commitment was made.
Portability
This skill is intentionally host-neutral. Use your agent's normal mechanisms to
load the references listed here. Do not assume a particular profile system, task
orchestrator, memory service, calendar provider, or response-handoff format.
1---2name: chief-of-staff-methodology3description: >-4 Prepare accountable executive decisions, decision support, briefings, information5 triage, calendar choices, and institutional memory. Use for chief of staff or CoS,6 executive operations, founder operations, operating rhythm, strategic attention,7 executive office, board materials, organizational sensing, team health, leadership8 transitions, gatekeeping, decision memos, executive briefing, strategic time,9 attention allocation, calendar triage, or meeting audits for a solo operator or organization.10 Do not use for generic personal assistance, employee surveillance, inferred11 commitments, automatic task mutation, meeting facilitation, org structure design,12 or business operating-process design; route to the owning specialist.13license: MIT14compatibility: No runtime dependency.15metadata:16 source: https://skillmd.com/skills/magnus919/chief-of-staff-methodology17 tags: chief-of-staff, cos, executive-operations, founder-operations, decision-support, operating-rhythm, strategic-attention18 source_repo: https://github.com/magnus919/hermes-profiles19 source_commit: "867a555"20 source_path: skills/chief-of-staff-methodology21 source_treatment: Adapted from supplied issue source material and substantially rewritten for host-neutral, privacy-aware use.22---2324# Chief of Staff Methodology2526The Chief of Staff supports an accountable leader's capacity to operate across27domains. This skill helps prepare, triage, coordinate, surface trade-offs, and28preserve decision context; it does not transfer the leader's authority.2930## Solo operators and organizations3132For a solo founder, the founder is the accountable decision-maker: prepare options,33trade-offs, an attention plan, and a review rhythm around their real decisions.34Do not invent a leadership team, delegated authority, or commitments. For an35organization, identify the executive sponsor and existing decision rights before36coordinating across teams. In both settings, prepare, coordinate, brief, and record;37the human decides and authorizes action.3839An executive operating rhythm here connects pending decisions, evidence, and review40dates. Route meeting facilitation and records to `meetings`, organizational41structure and reporting lines to `org-design`, and repeatable business-process42ownership and handoffs to `operational-design`. Use an authorized task-system skill43only for confirmed commitments under the task-creation discipline below.4445## When to Load4647Load this skill for executive-office work involving:4849- Information triage, gatekeeping, escalation paths, or decision rights.50- Decision memos, executive briefing, board materials, or preparation for an accountable decision-maker.51- Calendar triage, meeting audits, strategic time, or attention allocation.52- Cross-functional coordination where ownership, dependencies, or escalation need clarification.53- Transparent organizational sensing or team-health concerns.54- Institutional memory, leadership transitions, documented decisions, or commitments.55- Chief of staff, CoS, executive operations, founder operations, decision support,56 operating rhythm, or strategic attention that needs a bounded operating method.5758## When Not to Use5960Do not use this skill for generic personal errands or covert employee surveillance.61For meeting facilitation use `meetings`; for organization structure use `org-design`;62for business operating processes use `operational-design`.6364Do not use this skill as a meeting-transcript action-item generator or a general65backlog-capture mechanism. A recommendation, a discussion topic, or an inferred66next step belongs in a briefing or decision record unless an accountable owner67has confirmed a discrete commitment and a realistic due date. Use the authorized68task-system skill only after those conditions are satisfied.6970## What This Skill Provides7172This skill provides six methodology domains as progressive disclosure through73`references/`. Load the reference matching the task using your agent's normal74means; no specific profile, memory, calendar, or orchestration system is assumed.7576## Reference Files7778| Reference | Load when | File |79|---|---|---|80| Gatekeeping and triage | Mapping information to authority, access, and escalation | `references/gatekeeping-and-triage.md` |81| Executive briefing | Preparing decision-ready material or an executive update | `references/executive-briefing.md` |82| Leverage mechanisms | Improving the leader's operating system without false measurement | `references/force-multiplication.md` |83| Organizational sensing | Addressing team-health or organizational signals responsibly | `references/organizational-sensing.md` |84| Institutional memory | Recording decisions, commitments, and authorized handoffs | `references/institutional-memory.md` |85| Meeting and calendar triage | Reviewing meetings and calendar choices with the leader | `references/meeting-and-calendar-triage.md` |86| Source index | Checking provenance and the limits of source treatment | `references/source-index.md` |8788## Operating Method89901. Identify the accountable human decision-maker, the decision rights already delegated, and the decision or outcome at stake.912. Gather authorized evidence and label it as verified fact, assumption, reported concern, or unknown. Do not invent costs, timelines, authority, or stakeholder views.923. Route ordinary work to its authorized owner. Keep direct, protected routes open for safety, ethics, legal, HR, fraud, retaliation, and whistleblowing concerns.934. Prepare options and trade-offs, then give a clearly labeled recommendation when the request calls for one. The accountable human reviews and decides.945. Record only decision-relevant material under the access, retention, correction, and handoff rules in the applicable reference.9596## Task Creation Discipline9798**Applicability:** Only when creating or updating tasks in an authorized task system.99100A task is a record of a concrete, documented commitment, not a place to store101advice, aspirations, meeting summaries, inferred next steps, or recurring102leadership habits. Create a task only when the source establishes all of the103following:1041051. A discrete outcome or next action that can be completed or explicitly reviewed.1062. An accountable owner who has made, confirmed, or accepted the commitment.1073. A realistic due date grounded in an explicit deadline, an agreed review date,108 or context that supports a specific date. Never invent a date merely to fill109 a required field.1104. Enough provenance in the task or linked record for the owner to understand111 the commitment and correct it.112113Before creating the task, check all four conditions. If the source offers a114recommendation, a general principle, or an inferred action without an owner or115defensible due date, preserve it as a briefing observation or ask the accountable116human to confirm the commitment and date. Do not create the task.117118When a task is created, include the owner and due date in the creation request,119then read it back and verify both fields persisted. If either is absent or wrong,120repair it before reporting success. A past deadline is a triage signal: surface121it as overdue for an explicit reschedule, completion, or closure decision rather122than silently assigning a new date.123124## Accountable Human Authority125126This skill supports an accountable human leader. It may prepare, advise, triage,127synthesize, and surface trade-offs. It does not make employment, compensation,128disciplinary, legal, fiduciary, or other reserved decisions, and it does not129present an automated recommendation as a decision.130131Name the decision-maker and applicable approval or review path in consequential132artifacts. A CoS function can coordinate delegated work, but it must route work133outside that delegation to the authorized owner. Human review is required before134material is issued as the leader's position.135136## Privacy, Confidentiality, and Ethics137138Use only authorized, purpose-limited information. Prefer aggregate information139and the minimum data needed for the stated purpose. Be transparent about what is140collected, who can access it, how it is retained, and how people can correct it.141142Do not use covert monitoring, individual trust scores, dossiers, gossip maps,143quiet-quitting labels, hidden relationship profiling, or speculative judgments144about people. Confidentiality has limits: safety, harassment, fraud, legal, and145policy obligations may require escalation through authorized channels. Preserve146anti-retaliation protections and involve qualified HR, legal, safety, or ethics147professionals for matters in their remit.148149## Boundaries150151| Domain | Boundary | Use instead |152|---|---|---|153| Product definition and prioritization | This skill prepares or coordinates a decision; it does not define product strategy | `product-methodology` |154| Corporate or business strategy | This skill structures a leader's operating work; it does not set strategy | `strategy-frameworks` |155| Financial models and budgets | This skill may surface a resource question but does not build or validate a model | `financial-modeling` |156| Verification claims | This skill prepares artifacts but does not turn missing evidence into a pass | `verification-methodology` |157| Evidence presentation | This skill does not prescribe a research-artifact hierarchy | `artifact-pyramids` |158| Operational tooling | It does not automate mail, calendars, personal data stores, or task systems | Use the organization's authorized tools and policies |159160## Pitfalls161162- Treating triage as a private veto instead of a transparent route to the authorized owner.163- Hiding uncertainty, weak evidence, or an unresolved conflict to make a brief look decisive.164- Speaking as the leader without review, approval, and clear authorship.165- Treating people signals as proof of individual performance, intent, or protected-status issues.166- Storing personal impressions instead of durable, documented decision context.167168## Related Skills169170- `artifact-pyramids` for layered, inspectable decision artifacts.171- `financial-modeling` for assumptions-led financial analysis.172- `product-methodology` for product decisions and prioritization.173- `strategy-frameworks` for strategy choices and trade-offs.174- `verification-methodology` for evidence-backed completion claims.175- `slack` — channel triage and message search through the Slack Web API; confirmed posting only. The everyday read layer for "what was said, find it later."176- `notion` — knowledge search, page and database reads through the Notion API; confirmed edits only.177- `email` — transactional email sends and delivery verification (bounces, spam reports, event-webhook signature check) through SendGrid. Read-only discovery before any send.178179## Completion180181Complete when the requested brief, triage recommendation, attention plan, or decision182record identifies the human decision owner, evidence gaps, and next review or183escalation. Stop at missing authority or unavailable evidence; record the gap rather184than claiming a decision or commitment was made.185186## Portability187188This skill is intentionally host-neutral. Use your agent's normal mechanisms to189load the references listed here. Do not assume a particular profile system, task190orchestrator, memory service, calendar provider, or response-handoff format.