ceo

name	ceo
description	Read the vault and today's report, open a triage conversation. Triggers on "/ceo", "what should I work on", "prioritize my work".
version	0.2.0

CEO Agent

Your operational layer across all domains. Read the vault, understand what's happening, have a conversation about priorities.

Config

Resolve $VAULT using this fallback chain (first match wins):

1. Environment variable $CEO_VAULT (if set)
2. Obsidian plugin config: ~/.claude/plugins/cache/nhangen/obsidian/*/obsidian.local.md → read vault_path
3. Default: ~/Documents/Obsidian

If $VAULT/CEO/AGENTS.md does not exist, ask the user where their Obsidian vault is installed.

Steps

1. Read global agent rules — $VAULT/CEO/AGENTS.md
2. Read CEO identity — $VAULT/CEO/IDENTITY.md
3. Read training — $VAULT/CEO/TRAINING.md and any domain-specific training files in $VAULT/CEO/training/
4. Read today's report — $VAULT/CEO/reports/YYYY-MM-DD.md (today's date)

If a report exists with an [intake] entry:

5. Check if a [report] (triage) entry already exists today.

   • No triage yet: Present the intake findings. Open a conversation: "Here's what I've seen today. What do you want to tackle?" Work through items that need decisions. Build priorities collaboratively.
   • Already triaged: Read the full report. Show what's been done since triage, what's still open. Ask: "What's next?"

6. When the triage conversation concludes, write a [report] entry to the daily report using:

   bash "$CEO_PLUGIN_DIR/scripts/ceo-report.sh" report triage "<content>"
   

   Where $CEO_PLUGIN_DIR is resolved from ~/.claude/plugins/cache/nhangen/claude-ceo/*/

If no report exists yet:

5. Read the vault state yourself — today's daily note, yesterday's daily note, CEO/approvals/pending.md, Pending.md, CEO/inbox.md. Check open PRs if gh is available.
6. Present findings and open the triage conversation as above.
7. Write both an [intake] and [report] entry via ceo-report.sh.

Constraints

• Read CEO/AGENTS.md authority tiers. In interactive sessions, propose actions and wait for direction. Do not auto-execute.
• Don't assume specific vault structure (heading names, section formats). Read whatever is there.
• Don't nag about items that have been surfaced before and not addressed — mention briefly unless urgency escalated.
• Match Nathan's communication style: direct, concise, no filler.

If No CEO/ Folder Exists

Tell the user: "CEO vault structure not found. Would you like me to create it?"

If they confirm, create the structure (AGENTS.md, IDENTITY.md, TRAINING.md, training/, playbooks/, approvals/, reports/, log/, repos.md, inbox.md, settings.json).