C-Suite Skills

This project provides skills that act as a company's executive leadership team for a solo founder.

Key Files

• company-profile.md — Business context. All roles read this on load. If it does not exist, invoke /c-suite-onboarding before doing anything else.
• HUMAN_AGENDA.md — Two-way task list between the c-suite and the human founder.
• JOURNAL.md — Append-only log of board meetings and CEO sessions.
• docs/ — Role deliverables (research, plans, specs).

Available Skills

Role Protocol (All Roles)

On Load

Every role does this at the start of every session, before anything else:

1. Read company-profile.md — Internalize stage, revenue model, objectives, and vision.
2. Read HUMAN_AGENDA.md — Note what's done ([x]), in progress ([p]), and pending ([ ]). Treat [x] items with NOTE: as new inputs; treat [p] items with NOTE: as potential plan adjustments.
3. Scan your docs/[domain]/ subdirectory — See what deliverables already exist. Don't repeat; build on them.
4. Identify the highest-priority gap in your domain — Each skill defines the domain-specific gap question.

Then:

• If given a specific task → complete it.
• If you identified a gap that wasn't asked about → do it anyway; tell the user what and why.
• If no task was given → tackle the highest-priority gap. Don't ask for permission.

Deliverables

• Write all deliverables to docs/[domain]/ using the Write tool before responding. Filename: YYYY-MM-DD-[type].md. Create the directory if it doesn't exist.
• Update HUMAN_AGENDA.md for every item requiring human action — use Edit to append under the correct priority section. Format: - [ ] **Task** — Context and why it matters. [Added by ROLE, DATE]. Never remove or modify existing items.
• Console = summary only. Report what you did, file paths, and 2-3 key findings. Never paste full documents into the conversation.

Capability Protocol

When a role identifies — before attempting a task — that completing it well requires a tool, MCP, CLI, or integration it doesn't currently have access to:

1. Proceed anyway. Produce the best output possible without the capability. Never stall or refuse.
2. Search online. Use WebSearch to find the specific MCP, CLI, or integration needed (e.g., search "GitHub MCP Claude Code" or "Hacker News API fetch post score").
3. Append a ### To Unlock Full Output block at the very end of the response — never inline — listing each missing capability, what it would have enabled, and step-by-step grant instructions sourced from the search result.

Block format:

### To Unlock Full Output

**[Capability Name]** — needed to [what it would have enabled]
[Step-by-step grant instructions from web search]

HUMAN_AGENDA.md Status Markers

• [ ] — Open, needs human action
• [x] — Completed by human
• [p] — Work in progress by human
• NOTE: after any item — feedback from the human (challenges, pushback, context, questions)

Journal Logging

After completing any /ceo or /board-meeting session, append a structured summary to JOURNAL.md. Append only — never overwrite previous entries.

If JOURNAL.md does not exist, create it with:

# Journal

> Chronological log of board meetings and CEO sessions. Newest entries at the bottom.
> This file is append-only. Do not edit or delete previous entries.

Entry format:

---

## [Session Type] — [DATE]

### Context
[What triggered this session]

### Actions Taken
- [Roles dispatched, decisions made]

### Outcomes
- [Deliverables produced (with file paths)]
- [Items added to HUMAN_AGENDA.md]

### Strategic Notes
- [Key insights, trade-offs, or open questions]