/pipeline-update

name: pipeline-update
description: "Update CRM deals — move stages, change values and close dates, attach notes and activities, create follow-up tasks — with validation against pipeline rules, a before-and-after comparison, and calculated velocity, forecast, and pipeline-health impact. Writes to Salesforce, HubSpot, Zoho, or Pipedrive via the connected CRM MCP only after a mandatory execution gate: an Execution Summary preview plus explicit typed approval, logged through approval-manager.py. Triggers on \"/digital-marketing-pro:pipeline-update\", \"move this deal to negotiation\", \"update the deal value\", \"mark this deal closed-won\", \"which deals are stalled\". Reads the brand profile; pairs with /digital-marketing-pro:lead-import for creating deals and /digital-marketing-pro:executive-dashboard for bulk reporting."
disable-model-invocation: false
argument-hint: "[deal-name or stage]"

/digital-marketing-pro:pipeline-update

Purpose

Update deal and opportunity records in the CRM pipeline — move deals between stages, update values, add notes, and track pipeline velocity. Provides a clear before-and-after view of every change and calculates the downstream impact on pipeline metrics, giving both marketing and sales teams visibility into deal progression, forecast accuracy, and revenue pacing against targets. Designed for both individual deal updates and batch stage transitions, with built-in validation to prevent invalid stage skips and mandatory field gaps.

Use this command for pipeline changes that affect deal stage, value, or forecast. For creating new deals from leads, use `/digital-marketing-pro:lead-import` to bring leads into the CRM first, then use this command to manage their pipeline progression. For bulk pipeline reporting without individual updates, use `/digital-marketing-pro:executive-dashboard` instead.

Execution gate (MANDATORY — cannot be skipped)

1. Present the full preview — recipients / spend / changes / compliance — as an **Execution Summary** before touching any live system. 2. The user must type `yes` (or an equivalent explicit approval). ANY other input — ambiguous, implied, partial, or absent approval — cancels the run. 3. Never proceed on ambiguous input. Never auto-retry a failed execution; a failure needs human review before any re-run. 4. Record the approval with `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action create-approval --data '{"risk_level":"<tier>","summary":"..."}'` **before** executing, then `python "${CLAUDE_PLUGIN_ROOT}/scripts/approval-manager.py" --brand {slug} --action mark-executed --id {approval_id}` after the platform confirms success.

Input Required

The user must provide (or will be prompted for):

• **Deal identifier**: How to locate the deal — deal name, associated contact email, company name, or CRM record ID. If ambiguous, the system will present matching candidates for selection.
• **Updates to apply**: One or more changes — stage change (e.g., "Proposal Sent" to "Negotiation"), deal value update (increase, decrease, or split), close date adjustment, probability override, loss reason (if moving to closed-lost), or custom field modification
• **Notes or context**: Reason for the update, meeting summary, objection details, competitor intelligence, next steps, or any qualitative context to attach to the deal record as a timestamped note
• **Pipeline name (if multiple)**: Which pipeline the deal belongs to — relevant for businesses with separate pipelines for new business, renewals, upsells, partnerships, or different product lines
• **CRM platform**: Salesforce, HubSpot, Zoho, or Pipedrive — and the specific pipeline/opportunity object if the platform supports multiple pipeline types
• **Activity association (optional)**: Whether to log the update as a specific activity type — call, meeting, email, task, demo, or custom activity — with timestamp, duration, and participants
• **Follow-up actions (optional)**: Tasks to create as a result of this update — schedule next call, send proposal, loop in technical resource, create SOW, or set reminder for follow-up date with assignee and due date
• **Notification preferences (optional)**: Whether to notify the deal owner, account executive, or manager about this pipeline change — and via which channel (CRM notification, email, Slack)
• **Batch update scope (optional)**: If updating multiple deals at once — a list of deal identifiers with the same update to apply, or a filter criteria to select deals (e.g., "all deals in Discovery stage with close date before March 1")
• **Win/loss analysis fields (optional)**: If closing a deal — won/lost reason, competitor involved, deciding factor, lessons learned, and whether the contact should enter a win-back or referral sequence
• **Revenue recognition details (optional)**: For closed-won deals — contract terms (monthly/annual), start date, renewal date, one-time vs. recurring revenue split, and any discount or promotional pricing applied
• **Related deals (optional)**: Whether this update affects related deals — upsell opportunities, cross-sell deals, or renewal pipeline that should be created or updated based on this deal's stage change

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Check connected CRM and pipeline configuration**: Verify CRM connection status, retrieve available pipelines and their stage definitions (includin