most-prepared

name	most-prepared
description	Build a comprehensive meeting brief; not compact call prep.
metadata	{"short-description":"Build a comprehensive meeting intelligence brief"}

Most Prepared

Outcome

A high-signal briefing that anticipates context, stakeholder dynamics, decisions, objections, and the right next move.

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: Meeting and attendees, account and opportunity data, activity history, commitments, service issues, stakeholder map, relevant internal documents, and authorized current research.
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 all identities and relationships conservatively and note participants without verified CRM matches.
2. Synthesize what changed, customer priorities, commercial state, stakeholder dynamics, open commitments, likely objections, and internal constraints.
3. Verify consequential product, policy, pricing, legal, security, and customer claims against authoritative sources.
4. Prioritize decision-useful context; place optional background separately and label hypotheses and unknowns.

Required output

• Executive brief
• Participants and dynamics
• Account and deal state
• Recent timeline
• Decisions, commitments, and risks
• Likely questions or objections
• Recommended agenda and next move
• Sources and caveats

Actions and boundaries

Read-only unless the user separately authorizes follow-up, scheduling, or CRM changes.