Initial commit
This commit is contained in:
32
commands/build-automation.md
Normal file
32
commands/build-automation.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: build-automation
|
||||
description: Generates a marketing automation workflow with triggers, branching, waits, and success tracking.
|
||||
usage: /email-marketing:build-automation --trigger "form submission" --goal nurture --touches 6
|
||||
---
|
||||
|
||||
# Command: build-automation
|
||||
|
||||
## Inputs
|
||||
- **trigger** – entry event (form submission, product action, scoring threshold).
|
||||
- **goal** – nurture objective (education, onboarding, monetization, retention).
|
||||
- **touches** – number of total emails/SMS/push steps.
|
||||
- **channels** – optional cross-channel steps (email, in-app, SMS, webhooks).
|
||||
|
||||
## Workflow
|
||||
1. **Trigger Mapping** – confirm data source, frequency caps, and mutual exclusivity.
|
||||
2. **Journey Blueprint** – outline each step with wait times, conditional logic, fallback paths.
|
||||
3. **Data & Personalization** – list fields, lookups, and APIs required per touch.
|
||||
4. **QA Checklist** – testing matrix covering render, tracking, suppression, and compliance.
|
||||
5. **Launch Plan** – assign owners, go-live date, monitoring dashboards, rollback plan.
|
||||
|
||||
## Outputs
|
||||
- Visual workflow map (mermaid + textual summary).
|
||||
- JSON/YAML ready spec for MA platforms (e.g., HubSpot, Marketo, Iterable, Braze).
|
||||
- Measurement plan including alerting thresholds.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `automation-specialist` – converts plan into an executable workflow.
|
||||
- `segmentation` skill – ensures entry/exit criteria, suppression lists, and re-entry windows.
|
||||
- `ab-testing` skill – recommends experiment points within the flow.
|
||||
|
||||
---
|
||||
32
commands/design-campaign.md
Normal file
32
commands/design-campaign.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: design-campaign
|
||||
description: Creates full-funnel email campaign plans with assets, segmentation, and cadences.
|
||||
usage: /email-marketing:design-campaign --goal launch --audience startups --touches 5
|
||||
---
|
||||
|
||||
# Command: design-campaign
|
||||
|
||||
## Inputs
|
||||
- **goal** – conversion objective (launch, nurture, upsell, retention).
|
||||
- **audience** – persona, lifecycle stage, or segment key.
|
||||
- **touches** – number of emails in the sequence.
|
||||
- **offers** – optional incentives, resources, or events to feature.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Intake** – parse goal + audience to determine messaging pillars.
|
||||
2. **Audience & Personalization** – recommend segmentation logic, merge fields, dynamic modules.
|
||||
3. **Touch Matrix** – draft touch-by-touch objectives, subject lines, preview text, CTA focus, content notes.
|
||||
4. **Asset Checklist** – list creative needs (copy blocks, graphics, landing pages, tracking URLs).
|
||||
5. **Measurement Plan** – specify KPIs per touch, success thresholds, and experiment ideas.
|
||||
|
||||
## Outputs
|
||||
- Campaign overview (goal, target, primary offer, KPI table).
|
||||
- HTML-ready copy briefs with personalization notes.
|
||||
- QA checklist covering links, tracking, accessibility, and compliance.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `email-strategist` – requirements gathering and KPI translation.
|
||||
- `drip-campaigns` skill – ensures best-practice cadence and pacing.
|
||||
- `segmentation` skill – validates filters and suppression logic.
|
||||
|
||||
---
|
||||
32
commands/optimize-deliverability.md
Normal file
32
commands/optimize-deliverability.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: optimize-deliverability
|
||||
description: Diagnoses email deliverability issues and produces remediation steps.
|
||||
usage: /email-marketing:optimize-deliverability --issue spam-folder --domain example.com
|
||||
---
|
||||
|
||||
# Command: optimize-deliverability
|
||||
|
||||
## Inputs
|
||||
- **issue** – primary symptom (spam-folder, bounce-spike, low-open, blacklist, reputation-drop).
|
||||
- **domain** – sending domain or subdomain experiencing issues.
|
||||
- **volume_change** – optional volume delta % to assess sudden scaling.
|
||||
- **ip_pool** – optional dedicated/shared IP identifier.
|
||||
|
||||
## Workflow
|
||||
1. **Signal Intake** – gather metrics (opens, clicks, spam, bounces, blocklist hits, complaint rate).
|
||||
2. **Infrastructure Review** – authenticate SPF/DKIM/DMARC/BIMI status, TLS, reverse DNS, feedback loops.
|
||||
3. **Reputation Analysis** – evaluate Postmaster, SNDS, Talos, Barracuda, Spamhaus signals.
|
||||
4. **Audience Health** – inspect segmentation, engagement tiers, inactivity policies, data collection sources.
|
||||
5. **Content Audit** – scan for spam triggers, code issues, heavy imagery, link redirection.
|
||||
6. **Remediation Plan** – propose warmup ramps, segmentation filters, copy tweaks, infrastructure fixes.
|
||||
|
||||
## Outputs
|
||||
- Deliverability diagnostic report (tables for reputation, infrastructure, audience, content).
|
||||
- Action plan prioritized by impact vs effort.
|
||||
- Monitoring checklist with KPIs and time horizons.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `deliverability-analyst` – leads investigation and remediation plan.
|
||||
- `deliverability` skill – references playbooks for IP warmups, segmentation adjustments, authentication.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user