Morning intelligence briefing that surfaces the deals, patterns, and signals demanding attention right now. Use when user says "what should I focus on", "morning briefing", "what happened", "signals", "what needs attention", "daily update", or asks what changed since they last checked. Flips from pull-based to push-based — the data tells you what to work on.
Morning intelligence briefing that surfaces the deals, patterns, and signals demanding attention right now. Use when user says "what should I focus on", "morning briefing", "what happened", "signals", "what needs attention", "daily update", or asks what changed since they last checked. Flips from pull-based to push-based — the data tells you what to work on.
/octave-signals - Morning Intelligence Briefing
Your daily command center. Surfaces the deals that moved, objections trending up, competitors appearing, stakeholders going silent, and messaging themes gaining or losing traction — so you know exactly what to work on today.
Principles
Follow these standards during generation. Read each before producing output.
Content and language:
Editorial rules — no AI-isms, banned vocabulary, honest analyst tone
--focus <area> - Zoom into one section (deals, patterns, pipeline, content)
--segment <name> - Filter by segment
--motion <name> - Filter by Motion
Examples
/octave-signals # Full morning briefing (last 7 days)
/octave-signals --period today # What happened since yesterday
/octave-signals --period 2w # Broader two-week view
/octave-signals --focus deals # Just the deals that need attention
/octave-signals --focus patterns # Just emerging patterns
Instructions
When the user runs /octave-signals:
Step 1: Gather All Signal Data
Run these queries in parallel to gather the full picture. Use the period option to set date ranges (default: last 7 days).
list_findings({
query: "objections, business problems, questions or confusion about the offering, competitor mentions and comparisons, value prop presentations, proof points, use cases, and pain points",
startDate: "<period start>",
endDate: "<today>",
limit: 200
})
C. Previous Period Findings (for trend comparison)
list_findings({
query: "objections, competitor mentions and comparisons, value prop presentations, and proof points",
startDate: "<two periods ago>",
endDate: "<period start>",
limit: 200
})
When --focus is specified, show only that section with expanded detail:
--focus deals: Show the Deals section with additional context per deal — include last 3 interactions, all stakeholders, full finding history.
--focus patterns: Show the Patterns section with full finding breakdowns — include specific quotes, event links, week-over-week trend charts.
--focus pipeline: Show Pipeline Health with deal-level detail — list every deal that moved, every deal at risk, every new deal.
--focus content: Show Content Performance with usage rankings across all proof points, value props, and Motion ICPs.
Step 5: Drill Down
When user asks to dive deeper into any signal:
get_event_detail({
eventOId: "<event_oId>"
})
Present full context for the signal — the event, the finding, the deal history, and recommended actions.
Step 6: Act on Signals
When user wants to act on a detected gap:
Library Gap → Create/Update:
# If objection not in a Motion ICP cell, update that cell's narrative
update_motion_playbook({
motionPlaybookOId: "<motion_playbook_oId>",
instructions: "Add objection handling for: [detected objection] to the relevant Motion ICP narrative section"
})
# If competitor not tracked
search_knowledge_base({
query: "<competitor name>",
entityTypes: ["competitor"]
})
# If not found, suggest:
# /octave-library create competitor "[name]"
Deal Signal → Route to Skill:
Suggest the appropriate follow-up skill based on signal type:
search_knowledge_base - Match findings to library content
get_entity - Get entity details for context
Library Updates
update_entity - Apply detected gap fixes
create_entity - Create new entities for detected gaps
update_motion_playbook - Edit Motion Playbook narrative sections (e.g., add objection handling to a Motion ICP)
Error Handling
No Events in Period:
No activity found in the last [period].
This could mean:
No calls/emails have been synced recently
The period is too narrow — try --period 2w or --period month
CRM/email integration may need reconnecting
Check your integrations in Octave, or try a wider window.
No Findings Extracted:
Events found but no findings extracted yet.
Recent events may still be processing. Check back in a few minutes.
In the meantime, here's what happened (raw activity):
[Show event summary without finding analysis]
Insufficient Data for Trends:
Not enough historical data to detect trends.
I'll show you what's happening now, but trend analysis needs at least 2 weeks of data.
Keep using Octave and trends will appear in future briefings.
Related Skills
/octave-insights - Deep dive into specific finding types
/octave-pipeline - Deal-level coaching for flagged deals
/octave-win-loss-report - Pattern analysis across deal outcomes
/octave-battlecard-doc - Competitive intelligence for new competitors
/octave-train - Turn trending objections into team coaching
/octave-audit - Full library health check
/octave-library - Create/update entities for detected gaps
