Initial commit

commands/analyze-sequences.md

@@ -0,0 +1,33 @@
+---
+name: analyze-sequences
+description: Evaluates live or completed email sequences, highlighting performance, deliverability, and experiment results.
+usage: /email-sequence-orchestration:analyze-sequences --sequence "Expansion Play" --window 14d --detail full
+---
+
+# Command: analyze-sequences
+
+## Inputs
+- **sequence** – program name or ID to analyze.
+- **window** – time horizon (7d, 14d, 30d, custom date range).
+- **detail** – summary | full to control verbosity.
+- **segment** – optional audience filter (persona, tier, region).
+- **compare_to** – optional baseline sequence or control group.
+
+## Workflow
+1. **Data Pull** – collect MAP + CRM metrics (deliverability, engagement, pipeline impact) within specified window.
+2. **Health Diagnostics** – evaluate KPI attainment, drop-off points, inbox placement, and fatigue risk.
+3. **Experiment Readout** – summarize running/closed tests with confidence intervals and recommended actions.
+4. **Insights & Actions** – generate prioritized playbook (optimize cadence, refresh content, escalate issues).
+5. **Handoff** – prepare recap doc plus suggested backlog updates for architect + ops teams.
+
+## Outputs
+- Performance dashboard snapshot with KPIs by touch, persona, mailbox provider.
+- Deliverability + QA alert summary referencing `deliverability-lead` incident logs.
+- Experiment insights memo (winners, next tests, rollout guidance).
+
+## Agent/Skill Invocations
+- `experiment-analyst` – interprets tests and recommends next experiments.
+- `deliverability-lead` – correlates reputation signals with performance dips.
+- `cadence-design` skill – flags pacing issues causing fatigue.
+
+---

commands/automate-delivery.md

@@ -0,0 +1,33 @@
+---
+name: automate-delivery
+description: Configures MAP/CRM automation for the approved email sequence with routing, throttling, and QA hooks.
+usage: /email-sequence-orchestration:automate-delivery --sequence "Expansion Play" --platform marketo --start-date 2025-02-01
+---
+
+# Command: automate-delivery
+
+## Inputs
+- **sequence** – name or ID referencing the architecture produced by `plan-sequences`.
+- **platform** – marketing automation platform or ESP (Marketo, HubSpot, Braze, Salesforce).
+- **start-date** – planned launch date (YYYY-MM-DD) for scheduling.
+- **throttle** – optional sends/hour or batch size.
+- **approvers** – optional list of stakeholders required for sign-off.
+
+## Workflow
+1. **Pre-flight Checklist** – verify assets, personalization tokens, suppression lists, and compliance flags.
+2. **Routing Logic** – configure smart lists, triggers, and branching per segment plus fallback states.
+3. **QA Sandbox** – spin up test programs, send proofs, validate dynamic content + tracking links.
+4. **Governance Hooks** – enable monitoring (webhooks/logging), set up pause/resume controls, document owners.
+5. **Launch Plan** – publish schedule, warmup recommendations, and alert routing for real-time issues.
+
+## Outputs
+- Deployment runbook (steps, owners, environments, approvals) stored alongside automation project.
+- Platform configuration checklist with screenshots/IDs for programs, flows, and assets.
+- Alerting + rollback plan tied to deliverability and QA gates.
+
+## Agent/Skill Invocations
+- `marketing-ops-partner` (from lead nurture) or platform-specific ops agent for implementation support.
+- `deliverability-lead` – ensures cadence + authentication alignment.
+- `qa-gates` skill – enforces pre-flight checks before go-live.
+
+---

commands/plan-sequences.md

@@ -0,0 +1,33 @@
+---
+name: plan-sequences
+description: Builds multi-touch email sequence architectures with segments, offers, and testing roadmap.
+usage: /email-sequence-orchestration:plan-sequences "Expansion Play" --stage expansion --length 6
+---
+
+# Command: plan-sequences
+
+## Inputs
+- **name** – internal title for the sequence or program.
+- **stage** – lifecycle moment (onboarding, nurture, expansion, win-back).
+- **length** – number of touches (integer) or timeframe (e.g., 6weeks).
+- **audiences** – optional CSV/list describing primary segments.
+- **offers** – optional summary of value props to rotate.
+
+## Workflow
+1. **Brief Intake** – confirm goals, ICP, compliance constraints, and triggering events.
+2. **Segment Mapping** – align audiences with triggers, suppression rules, and dynamic content tokens.
+3. **Sequence Drafting** – define each touch with timing, channel, offer, personalization notes.
+4. **Testing Roadmap** – pair priority steps with hypotheses, sample sizes, and guardrails.
+5. **Handoff Packet** – consolidate creative requirements, data needs, and measurement plan.
+
+## Outputs
+- Sequence architecture table (touch #, delay, audience, CTA, owner, KPI).
+- Personalization requirements matrix (field, fallback, source system).
+- Experiment backlog prioritized by potential lift + complexity.
+
+## Agent/Skill Invocations
+- `email-architect` – leads overall journey design and architecture.
+- `cadence-design` skill – ensures spacing and pacing best practices.
+- `experiment-analyst` – partners on testing roadmap creation.
+
+---