Plan Deal Strategy

Context-Gathering Intake

Whenever this skill asks for context, strongly prefer using the answers-ask-user-input skill and the ask_user_input tool over other tools such as request_user_input; otherwise ask directly in the conversation.

Turn active-deal evidence or clearly supplied offer context into a practical strategy for advancing a sale or shaping an initial sales motion. This skill owns the deal map, buying committee, negotiation posture, objections, sequencing, and action plan; it is not first-call prep, data-first prospecting, or a writeback workflow.

Common Skill Instructions

MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.

Key Dependency Categories

These categories are particularly important for this workflow; use other sources only when they materially improve the strategy.

• [Blocking] ~~CRM for authoritative account and opportunity identity, stage, amount, close date, owner, contacts, and recent activity. It blocks the default active-deal strategy path unless sufficiently grounded deal truth is already in context.
• ~~Meeting Transcripts for stakeholder language, objections, commitments, decisions, procurement signals, and call continuity
• ~~Email for customer-facing progression, approvals, negotiation, legal/procurement exchange, and unanswered asks
• ~~Internal Messaging for internal blockers, owner alignment, escalation paths, and execution risk
• ~~Knowledge & Files for account plans, mutual action plans, implementation docs, risk logs, and strategy artifacts
• ~~Calendar for upcoming decision forums, executive meetings, procurement/legal milestones, and timing pressure
• ~~Sales Intelligence only when it sharpens a stakeholder or company hypothesis after the deal is anchored