Initial commit
This commit is contained in:
32
commands/configure-workflow.md
Normal file
32
commands/configure-workflow.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: configure-workflow
|
||||
description: Produces implementation instructions for building the automation inside MAP/CRM tools, including QA steps.
|
||||
usage: /marketing-automation:configure-workflow --journey onboarding --platform hubspot
|
||||
---
|
||||
|
||||
# Command: configure-workflow
|
||||
|
||||
## Inputs
|
||||
- **journey** – reference journey ID or description.
|
||||
- **platform** – automation platform (hubspot, marketo, braze, iterable, customerio, etc.).
|
||||
- **assets** – optional list of email/SMS/push templates to wire.
|
||||
- **qa_mode** – true/false to include full regression suite.
|
||||
|
||||
## Workflow
|
||||
1. **Blueprint Sync** – pull orchestration diagram + requirements.
|
||||
2. **Platform Mapping** – translate logic into platform-specific objects (smart lists, workflows, campaigns, journeys).
|
||||
3. **Configuration Steps** – detailed instructions for triggers, branches, waits, webhook/API calls, personalization tokens.
|
||||
4. **QA Matrix** – build test plan (seed recipients, device/browser, fallback paths, compliance checkpoints).
|
||||
5. **Launch Checklist** – approvals, scheduling, monitoring, rollback plan.
|
||||
|
||||
## Outputs
|
||||
- Step-by-step build guide with screenshots/snippets.
|
||||
- QA checklist and evidence log template.
|
||||
- Launch readiness form (owners, go-live date, monitoring links).
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `nurture-operator` – executes build tasks.
|
||||
- `workflow-testing` skill – ensures QA rigor.
|
||||
- `data-orchestrator` – validates data/suppression wiring.
|
||||
|
||||
---
|
||||
32
commands/monitor-automation.md
Normal file
32
commands/monitor-automation.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: monitor-automation
|
||||
description: Generates reporting + alerting plan to track automation health, experiment performance, and SLA compliance.
|
||||
usage: /marketing-automation:monitor-automation --journey onboarding --window 14d --metrics "activation,retention"
|
||||
---
|
||||
|
||||
# Command: monitor-automation
|
||||
|
||||
## Inputs
|
||||
- **journey** – automation identifier.
|
||||
- **window** – reporting cadence (7d, 14d, 30d, rolling).
|
||||
- **metrics** – comma-separated KPIs (activation, retention, revenue, NPS, pipeline).
|
||||
- **experiments** – optional list of A/B/C tests to track.
|
||||
|
||||
## Workflow
|
||||
1. **KPI Mapping** – align goals to metrics, data sources, attribution windows.
|
||||
2. **Instrumentation Audit** – confirm events/fields exist, dashboards, alerts, and experiment IDs.
|
||||
3. **Insight Generation** – highlight drop-offs, bottlenecks, fatigue, list growth, deliverability, suppression trends.
|
||||
4. **Action Plan** – recommend experiments, content refresh, cadence tweaks, or routing updates.
|
||||
5. **Governance** – log changes in journey changelog, assign owners, set follow-up dates.
|
||||
|
||||
## Outputs
|
||||
- Dashboard spec (Looker/Tableau/GDS) plus SQL snippets.
|
||||
- Weekly digest template with insights + recommended actions.
|
||||
- Alert configuration guide (Amplitude/Braze/Husky) for SLA breaches.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `data-orchestrator` – ensures accurate instrumentation.
|
||||
- `workflow-testing` skill – sets up regression tests/alerts.
|
||||
- `lifecycle-mapping` skill – contextualizes metrics by stage.
|
||||
|
||||
---
|
||||
33
commands/orchestrate-journey.md
Normal file
33
commands/orchestrate-journey.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: orchestrate-journey
|
||||
description: Generates an end-to-end automation blueprint with trigger logic, steps, and measurement.
|
||||
usage: /marketing-automation:orchestrate-journey --goal onboarding --persona founders --channels "email,SMS,in-app"
|
||||
---
|
||||
|
||||
# Command: orchestrate-journey
|
||||
|
||||
## Inputs
|
||||
- **goal** – lifecycle stage or desired outcome (onboarding, expansion, renewal, retention).
|
||||
- **persona** – audience segment with shared needs.
|
||||
- **channels** – comma-delimited list of active channels.
|
||||
- **length** – optional number of total steps.
|
||||
- **constraints** – legal, compliance, or SLA notes.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Parsing** – gather goals, KPIs, constraints.
|
||||
2. **Trigger & Entry Mapping** – define events, qualification, suppression, re-entry rules.
|
||||
3. **Journey Design** – outline each step with channel, content objective, personalization, fallback logic.
|
||||
4. **Data/Asset Plan** – list required fields, APIs, assets, owners, and deadlines.
|
||||
5. **Testing & Measurement** – propose QA plan, launch gates, dashboards, experiments.
|
||||
|
||||
## Outputs
|
||||
- Journey diagram (mermaid) with branching logic.
|
||||
- Configuration spec (JSON/YAML) for MAP/CRM systems.
|
||||
- Measurement plan with KPIs, alerts, and experiment backlog.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `journey-architect` – drives strategy and blueprint.
|
||||
- `lifecycle-mapping` skill – enforces best-practice cadence and segmentation.
|
||||
- `data-orchestrator` – confirms data requirements.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user