close-plan

name	close-plan
description	Build a close plan; label unagreed commitments.
metadata	{"short-description":"Build an evidence-based mutual close plan"}

Close Plan

Outcome

A sequenced plan from current state to decision and implementation, with owners, dependencies, and proof of agreement.

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: Target outcome and date, current stage, buyer process, stakeholders, remaining technical, commercial, security, legal, procurement, and implementation milestones.
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. Work backward from the target outcome and include realistic review, approval, and contingency time.
2. Distinguish customer-agreed milestones, seller assumptions, internal tasks, and unresolved dependencies.
3. For each milestone define owner, due date, dependency, completion evidence, and consequence of delay.
4. Surface impossible or internally inconsistent timelines rather than compressing them silently.

Required output

• Close objective and confidence caveat
• Milestone plan
• Critical path and decision dates
• Open assumptions
• Immediate next actions

Actions and boundaries

Create tasks or update close-plan fields only after the user approves the exact items.