| name | weekly-recap |
| description | Recap a seller's week; not a daily or team view. |
| metadata | {"short-description":"Summarize weekly progress and next steps"} |
Weekly Recap
Outcome
A concise, evidence-backed recap of progress, setbacks, activity, learning, and next priorities.
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
- Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
- Retrieve the minimum authorized evidence needed from the following inputs: Opportunity changes, completed and overdue activities, meetings, new leads, wins, losses, customer issues, and next-week commitments.
- Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
- Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
- Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.
Analysis rules
- Compare the week-end state with the start-of-week state and distinguish movement from static inventory.
- Highlight outcomes rather than activity volume alone; connect significant activity to customer or revenue progress where supported.
- Separate wins, risks, slipped commitments, and unresolved decisions.
- Call out incomplete capture or records updated after the reporting window.
Required output
- Week in brief
- Meaningful wins and movement
- Risks, slips, and open loops
- Metrics with definitions
- Next-week priorities
Actions and boundaries
Remain read-only unless the user explicitly asks to publish or update a recap elsewhere.
