outboundlisted

# Outbound - Outbound Sales Execution A skill that sequentially reaches out to prospects on the sales list via email, contact forms, SNS DMs, and playbook-driven platform channels. For each prospect, sends a message via an available channel and records the result in the DB. After all processing, generates a summary report. **Pace sends serially — don't parallelize.** Sub-agents for sub-tasks (drafting, page / form inspection) are encouraged; concurrent sends are not — they trip provider rate limits. A strong default, not a hard rule. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there (data storage, MCP error handling, document writes, output discipline). ## Steps ### 1. Setup - Project ID: `$0` (required) - Approach count: `$1` (default: 30) **Compliance pre-flight (run before anything else).** Call `mcp__plugin_leadace_api__get_compliance_status`. If `ready: false`, **abort immediately** — load nothing else. Report the `missing` fields, point the user at `fix_url` (e.g. `https://app.leadace.ai/workspace-settings`), and tell them to re-run once saved. Load `mcp__plugin_leadace_api__get_document` (`projectId: "$0"`) for `slug: "business"` and `slug: "sales_strategy"`. Sections that matter: - **Outreach mode**: `precision` (deep personalization) or `volume` (template-based semi-personalization). Always carries a concrete value — read it, don't assume a default - **Sales channels**: tac