odoo-draft-followup

/odoo-draft-followup

Single-purpose slash command for sales follow-up email drafting. Chains the odoo-deal-followup skill with a save-to-file step.

When to use

Invoke when you have a stalled or at-risk deal and need a follow-up email today. The skill analyzes deal context, assesses risk, suggests a next-best action, then drafts an email for review before sending.

Type: /odoo-draft-followup [customer-label]

Optional: supply customer label on the command line (e.g., Customer A). If omitted, the command will prompt you for it.

Hard rules

• Deal context is a request input: CRM metadata and pipeline rules arrive in the request itself (orchestrator structured data, or the sales user stating them). Nothing on disk stores them - do not go looking for a file. Resolve <SHARE_DIR>/<ISOLATE_DIR> once per ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md before writing the draft; substitute the captured absolute path - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit. When a fact about the customer's Odoo deployment matters, resolve the series per ${CLAUDE_PLUGIN_ROOT}/snippets/project-facts-resolution.md.
• Use what the caller already gave, then ask only for gaps: deal details are usually already in the request. Never make a human retype what is present. Optionally enrich from a live CRM/ERP/email integration if one exists - but never assume one; this command must work for an agent with only the request text and local files. Ask only for fields still unresolved:
  • Customer label or short name (e.g., "ABC Manufacturing")
  • Last touch date - only if not already provided
  • Current pipeline stage - only if not already provided
  • Prior commitments or blockers (e.g., "waiting on PO", "evaluating competing offer")
• Save without asking: write the draft under <ISOLATE_DIR>/followups/ and report its path; a user who wants changes says so and the command redrafts.
• No auto-send: This command only drafts. It does not send email, update CRM systems, or trigger workflows.