daily-briefing

name	daily-briefing
description	Prioritize a seller's day; not weekly reporting.
metadata	{"short-description":"Build a prioritized seller plan for today"}

Daily Briefing

Outcome

A realistic day plan that connects meetings, deadlines, pipeline movement, and customer risk.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Today's calendar, overdue and due tasks, active opportunities, recent changes, unanswered customer items, and user priorities.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Resolve the user's working date, timezone, role, and available time before ordering work.
2. Prioritize fixed-time commitments first, then revenue or customer risk, then high-leverage preparation and follow-up.
3. Explain why each item matters today and identify the underlying record or event.
4. Do not overload the plan: distinguish must-do, should-do, and if-time items and surface schedule conflicts.

Required output

• Morning headline
• Time-aware agenda
• Top three priorities with rationale
• Risks and overnight changes
• Preparation and follow-up checklist

Actions and boundaries

Draft tasks or calendar changes only when useful; obtain confirmation before creating or rescheduling them.