---
name: recon-daily-brief
description: Use when the user asks for their morning standup, daily pipeline read, or "what should I focus on today" via Recon. Pulls today's brief from Recon MCP, summarises in priority order, and queues actions.
---

# Recon: daily brief skill

This skill turns the Recon MCP daily brief into a priority-ordered standup read. Invoke it when the user says any of: "morning brief", "what should I focus on today", "Recon standup", "daily pipeline read", "what changed in the pipeline".

## What this skill does

1. Calls `recon.get_workspace_summary` to get the headline numbers (tier-1 ARR, drift alerts, recommendations awaiting response, verdicts measured this week).
2. Calls `recon.get_brief` to pull today's recommendations.
3. Calls `recon.list_recommendations` filtered to the last 7 days for context.
4. Returns a one-screen summary the user can read in 30 seconds.

## Output shape

Return three sections in this order:

**State of the pipeline** — three lines max. Tier-1 ARR + delta if available, count of recs awaiting response, count of drift alerts active.

**Today's brief** — for each section in the brief, render:
- Headline + segment + tier
- One-sentence summary of the recommendation
- Citation count (deals/companies/segments)
- Suggested action (Take it / Skip / Already did)

**What changed in the last 7 days** — verdicts measured, drift alerts that fired, scout suggestions that landed. Skip if empty.

## Tone rules

- Plain English. No emojis.
- Bold every numeric stat (currency, percentage, count, duration) using markdown.
- Never invent a number. If a metric isn't returned by Recon, say so.
- Default to action: end every recommendation summary with what the user could do this week.

## When NOT to use this skill

- The user is doing deep pipeline analysis (use `recon-pipeline-review` instead).
- The user is researching one company (use `recon-deal-research` instead).
- The user is refining their ICP (use `recon-icp-refresh` instead).

## Recommendation responses

When the user says "take it on rec X" or "skip rec X", call `recon.respond_to_recommendation` with the appropriate response_type and confirm the outcome cron will measure it at 30/60/90 days.