ops-leadgen

# ops-leadgen Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). Wraps `my-project-leadgen` CLI for the daily leadgen review-and-send loop. **Repo:** `~/Projects/my-project-b2b-leadgen` **DB:** `~/Projects/my-project-b2b-leadgen/leads.db` (gitignored) **Run with Doppler:** `doppler run --project my-project-b2b-leadgen --config dev -- my-project-leadgen <cmd>` ## Argument routing | Argument | Action | | -------------------- | ------------------------------------------------ | | `review` (default) | Show pending drafts one-by-one, approve or skip | | `send --draft-id N` | Send a single approved draft (Rule-6 gated) | | `usage` | Print today's Apollo reveals + Apify runs | | `scrape [--limit N]` | Discover new NL HR contacts via Apollo | | `enrich` | Run Apify enrichment on unenriched leads | | `draft` | Generate Claude NL/EN drafts for undrafted leads | ## Review + send flow (Rule 6) **NEVER send multiple drafts in one turn. Each send is a separate staged-draft → approval → send cycle.** 1. Run `my-project-leadgen review` (or fetch pending drafts from DB directly) 2. For each pending draft, show the user: - Lead: name, title, company, email...