Workflow Commands Reference

All the /cmo-* commands available in Coppermind, organized by when you use them. These are high-level workflows that orchestrate multiple MCP tools behind the scenes -- you just say what you need.

Type /cmo or /cmo-help at any time for a quick reference.

---

Daily Operations#

Commands you reach for every day.

Morning Briefing -- /cmo-brief with no client#

Start your day with a cross-client summary: today's meetings, overdue items, recent activity, and sprint deliverables. Run /cmo-brief with no client name (and no active client mind) to get the cross-client view.

/cmo-brief

What you get:

• Today's meetings with client matches (if Google Calendar is connected)
• Clients needing attention (overdue items, stale relationships)
• Current sprint deliverables due this week
• Prompt to prep any upcoming meetings

When to use it: First thing in the morning. Before you open your inbox.

---

/cmo-brief -- Client Briefing (alias /cmo-br)#

Get a full context dump for one client, or a cross-client overview when no client is specified.

/cmo-brief Acme
/cmo-brief

Single-client mode (client name provided or active client mind set): Produces a comprehensive state dump -- client overview, last meeting, open action items, recent activity, campaign status, upcoming deadlines, rock pacing, and brand voice snapshot. Saved automatically as a report.

Cross-client mode (no active client mind, no arguments): Produces a morning overview -- today's meetings, clients needing attention, and this week's sprint deliverables across all clients.

When to use it: When you need to re-load context on a client you have not touched in a few days. Before a strategy session. Or first thing in the morning for a cross-client view.

See also: Client Briefing guide for full details.

---

/cmo-prep -- Interactive Meeting Prep (alias /cmo-pr)#

Prepare a brief for an upcoming meeting, then interactively drill into specific topics before you walk in.

/cmo-prep
/cmo-prep Acme

What happens:

1. If your calendar is connected, it auto-detects your next meeting and matches it to a client; otherwise it asks which client
2. Generates a meeting brief with stakeholders, open items, and recent context
3. Offers interactive follow-up: "Want more detail on anything before the call?"
4. You can ask about specific stakeholders, dig into decisions, or review commitments

Tip: With Google Calendar connected, just run /cmo-prep with no arguments before a meeting block and it finds the next call for you.

See also: Interactive Meeting Prep guide for the full workflow.

---

/cmo-write -- Post-Meeting Follow-Up Email#

Draft a follow-up email after a client meeting, written in your voice (not the client's brand voice).

/cmo-write

What you get: A 3-4 paragraph email with:

• Brief recap of what was discussed
• Key decisions made (bulleted)
• Action items with owners and deadlines
• Next steps or next meeting date

Details:

• Uses your personal voice profile (say "set up my writing voice" first for best results)
• Pulls context from the most recent meeting brief and memories
• After you approve, marks the follow-up as sent in the meeting log

On a prospect mind (sales mind): The follow-up adapts to the current pipeline stage. Coppermind checks deal health, loads stored objections and buying signals, and structures the email to match where the deal stands:

Stage	What the follow-up emphasizes
Lead	Pain point recap, low-pressure discovery call ask
Discovery	Key discussion points, addresses 1-2 objections, proposes next step
Proposal	References the proposal, tackles top objection, highlights buying signals
Negotiation	Resolves remaining objections, proposes a close date
Closed Won	Onboarding next steps, reminder to convert the client mind to a client mind
Closed Lost	Professional close, asks for feedback, stores learnings

The deal health score (e.g., "72/100 - healthy") is shown as context for you -- not included in the email. If the follow-up implies a stage change, Coppermind suggests advancing the pipeline.

When to use it: Within an hour of finishing a client or prospect call. The faster you send follow-ups, the more professional you look.

---

/cmo-act -- Cross-Client Action Items#

See every open commitment across all clients, grouped by urgency.

/cmo-act

What you get:

• Overdue items with how many days overdue
• Items due this week
• Open items without due dates
• Total count across all clients

When to use it: Daily during your morning review. Weekly before your planning session. Any time you feel like something is slipping.

---

Weekly Review -- just ask#

Cross-client summary for the work week: meetings held, follow-ups sent, new knowledge captured, open items. There's no slash command -- just ask in plain English.

"How did this week go?"
"Give me my weekly review across all clients"

What you get: A per-client scoreboard with meetings, follow-up status, new memories by type, and open commitments.

When to use it: Friday afternoon. Or Monday morning to see last week.

---

/cmo-ingest -- Multi-Source Ingestion Hub#

Scan for content across all connected sources and ingest it into the correct client minds. Supports three source types with an interactive menu showing available counts.

/cmo-ingest
/cmo-ingest notes
/cmo-ingest slack
/cmo-ingest vault

Three sources:

Source	What It Pulls	Cap Per Run
Note-taker transcripts	Granola, Otter, Fathom, etc. -- meetings logged but not yet ingested	10 transcripts
Slack channel history	Messages from client Slack channels (fuzzy channel match, watermark tracking, noise filtering)	200 messages
Vault file transcripts	Obsidian vault files (stub/dupe filtering, cross-source dedup)	15 files

What happens:

1. Shows an interactive menu with available sources and counts
2. You pick a source (or pass it as an argument to skip the menu)
3. Fetches content from the selected source
4. Runs extraction pipeline on each item
5. Stores memories in the matched client mind
6. Deduplicates across sources so the same content isn't ingested twice

Requires: At least one source MCP connected (Granola, Slack, or Obsidian). Run with no arguments to see which sources are available and how many items are pending.

---

/cmo-connect -- Pull Data from Any MCP#

Bridge data from Granola, Gmail, Slack, or other connected MCPs into Coppermind memories.

/cmo-connect pull my last 3 Granola meetings into the right clients
/cmo-connect search Gmail for emails from sarah@acme.com about the rebrand
/cmo-connect pull recent Slack messages from #acme-marketing

When to use it: When you have data in another tool that should become client memories. Good for initial onboarding or catching up after a period without ingestion.

---

Content Creation#

Commands for writing and reviewing client-facing and CMO-facing content.

/cmo-write -- Write and Review Content#

Write or review content using a multi-expert panel. Automatically uses the correct voice (client brand voice for their audience, your CMO voice for emails to clients).

/cmo-write a LinkedIn post about our Q2 results
/cmo-write review this: "We offer best-in-class solutions..."
/cmo-write an email announcing our new service offering

Modes:

• Create: "write", "draft", "create", "compose" triggers writing mode
• Review: "review", "critique", "improve" triggers expert review mode

Voice selection: Content for the client's audience (blog, social, newsletter) uses the client's brand voice. Content from you to the client (follow-up, proposal) uses your personal voice.

On a prospect mind (sales mind): Instead of loading campaign history (which doesn't exist for prospects), Coppermind automatically searches for stored objections, buying signals, pain points, and competitive alternatives, and feeds them to the expert panel as sales context. Common content types on a prospect mind:

Content type	What makes it work
Proposal / SOW	References specific pain points and buying signals; proactively addresses stored objections
Follow-up email	Stage-aware structure (same logic as /cmo-write)
Objection-handling email	Pulls the specific objection from memory, structures a response
Sales deck / one-pager	Benefits mapped to stored pain points; clear CTA

When objection memories exist, an Objection Handler expert joins the panel to review content against known concerns and flag anything that could trigger an unaddressed objection.

---

/cmo-write -- Batch Content Creation#

Write the same type of content for multiple clients in one session.

/cmo-write write social posts for all my clients
/cmo-write draft newsletters for Acme and 5 Star

What happens: Switches between clients automatically, loads each one's brand voice, writes content in their voice, and presents everything together with clear client separators.

When to use it: Content production days. When you need to produce social posts, newsletters, or blog outlines for multiple clients at once.

---

Expert Panels (just ask)#

For deeper strategic work, Coppermind convenes a multi-expert panel -- several domain-specific perspectives analyze your situation and produce actionable recommendations, using the client's brand voice, campaign history, and stored context. You don't need a special command for each one. Switch to the client and ask in plain English -- Coppermind picks the right panel. Each works in two modes: build (create from scratch) or review (critique something you paste).

Ask for...	What you get
"Plan a spring campaign for Acme's new service"	Multi-channel campaign plan from brand voice + past performance
"Build a Q2 strategy deck for Acme"	Strategy / QBR presentation
"Write a proposal for Acme's Q3 engagement"	Proposal or SOW in your CMO voice (also /cmo-write)
"Write Acme's March performance report"	Performance report from campaign history + cadence
"Run a full marketing audit for Acme"	First-30-days detective work: stack, performance, competitors, team
"Build an SEO strategy for Acme"	SEO plan from positioning, keywords, content inventory
"Develop positioning for Acme"	The Positioning Protocol: avatars, competitive map, promise, proof
"Audit the marketing budget for Acme"	Spend/vendor/ROI review with reallocation recommendations
"Build a lead nurture sequence for Acme"	Email nurture / drip sequence from avatar data + brand voice
"Assess the marketing team at Acme"	Team structure, skill gaps, hire-vs-outsource recommendation

Say "review …" and paste content to get the same panels in critique mode.

---

/cmo-kickoff -- Client Kick-Off#

/cmo-kickoff plan the kick-off for Acme
/cmo-kickoff starting a new engagement with Bluebell

Structures the first 30 days of a new engagement: kick-off call agenda, timeline, credentials, deliverables, and quick wins.

---

Client Lifecycle#

Commands for major milestones in a client engagement.

/cmo-handoff -- Client Handoff Document (alias /cmo-ho)#

Generate a comprehensive handoff document when a client engagement ends. This is the "deliverable client mind" -- the client gets an AI that knows their brand.

/cmo-handoff
/cmo-handoff Acme

What you get: A client-safe package containing:

• A preflight with included memory count, exclusion counts, and raw-document status
• Full brand DNA (voice, positioning, messaging, stakeholders, content themes)
• Campaign history and outcomes
• Key decisions and their rationale
• Open items and recommended next steps
• Brand voice examples and anti-patterns
• Company context and stakeholder profiles

Private, sensitive, internal CMO, hidden, non-active, and unknown-sensitivity memories are excluded before the handoff is rendered.

When to use it: At the end of a client engagement. This is the killer differentiator -- the client walks away with a document that lets their next CMO (or internal team) pick up without starting from zero.

See also: Client Handoff guide for the full workflow.

---

/cmo-quarter-transition -- Quarter Transition (alias /cmo-qt)#

Orchestrate the interactive transition between EOS quarters when the client uses EOS or quarterly goals: close out rocks, update cadence, carry forward work, and capture retrospective insights.

/cmo-quarter-transition
/cmo-quarter-transition Acme

What happens:

1. Reviews current quarter rocks -- marks complete, dropped, or carried forward
2. Captures a brief retrospective on what worked and what did not
3. Sets up the new quarter with fresh rocks and updated cadence
4. Carries forward open commitments and unresolved issues

When to use it: At the end of each 90-day quarter. Usually during the final week of the quarter or the first day of the new one.

See also: Quarter Transition guide for the full walkthrough.

---

Quarterly and Sprint Cadence#

/cmo-quarterly -- Quarterly Review#

/cmo-quarterly
/cmo-quarterly Q4 2025

Generates a quarterly review for the active client: decisions made, campaigns run, rocks achieved, issues resolved, and lessons learned.

---

Sprint or Quarter Retrospective -- just ask#

There's no separate command -- ask Coppermind to run a retro and it convenes the panel (Rock Scorekeeper, Sprint Analyst, Campaign Evaluator, Team Dynamics Observer, Forward Planner).

"Run a sprint retro for Acme"
"Q1 retrospective for Acme -- how did we do?"

• Sprint mode: reviews the last 2-week sprint
• Quarter mode: reviews the full 90-day quarter

---

How These Commands Work Together#

A typical day for a fractional CMO using Coppermind:

Time	Command	What It Does
8:00 AM	/cmo-brief	See the day's landscape
8:05 AM	/cmo-brief Acme	Re-load full context on the first client of the day
9:45 AM	/cmo-prep	Interactive meeting prep for the 10:00 call
11:00 AM	/cmo-write	Draft and send the follow-up email
11:05 AM	/cmo-ingest	Ingest the meeting transcript
1:45 PM	/cmo-prep	Prep for the 2:00 call
3:00 PM	/cmo-write	Draft a blog post in the client's voice
4:30 PM	/cmo-act	Check what is still outstanding
Friday	"How did this week go?"	Week-in-review across all clients
End of sprint	"Run a sprint retro"	What went well, what needs to change
End of quarter	/cmo-quarter-transition	Close rocks, set up next quarter
End of engagement	/cmo-handoff	Generate the client's deliverable client mind

---

Tips#

• You do not need to switch clients first for cross-client commands. /cmo-brief (no arguments), /cmo-act, /cmo-ingest, and the weekly review ("how did this week go?") work across all clients automatically.
• Switch to the client first for per-client commands. Everything else requires an active client. Or pass the client name as an argument (e.g., /cmo-brief Acme).
• Expert panels work in both modes. Ask to "build" or "plan" to create from scratch. Ask to "review" or "critique" and paste content to get expert feedback.
• Set up your personal voice early. Anything that writes as you (follow-ups, proposals, handoffs) works better once you've said "set up my writing voice." Without it, output defaults to a neutral professional tone.
• Combine with meeting prep. After /cmo-brief shows your meetings, run /cmo-prep (it auto-detects your next calendar meeting) or say "prep my meeting with [client]" for a full brief.
• Use /cmo-brief to re-orient, /cmo-prep to prepare. Brief is for "catch me up on this client." Prep is for "I have a meeting in 15 minutes."
• Most commands have short aliases. /cmo-br for brief, /cmo-pr for prep, /cmo-ho for handoff, /cmo-qt for quarter transition, /cmo-in for ingest. /cmo-act is the cross-client action-items command.