engagement
The engagement command orchestrates a complete 12-part marketing methodology workflow for a brand, guiding users sequentially through intake, strategy documents, planning, and improvement cycles. Use this command to launch a new engagement after a brand profile is established, track progress across parts, validate deliverables at quality gates, and resume interrupted engagements via checkpointing.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/indranilbanerjee/digital-marketing-pro/HEAD/commands/engagement.md -o ~/.claude/commands/engagement.mdengagement.md
# /digital-marketing-pro:engagement — 12-Part Engagement Workflow
The engagement command family runs a complete marketing engagement using the 12-Part methodology. Every brand engagement runs through 12 parts in sequence, producing a canonical set of files at each stage.
This command is the entry point. It invokes the [engagement-workflow](../skills/engagement-workflow/SKILL.md) skill, which delegates to part-specific skills (four-core-documents, client-validation-document, growth-plan, yearly-planner, continuous-improvement-loop).
## Subcommands
### `/digital-marketing-pro:engagement start <brand-slug> <engagement-id>`
Initialise a new engagement. Creates the directory tree, writes `_engagement.json`, walks the user through Part 1 Stone vs Opinion intake.
**Example:**
```
/digital-marketing-pro:engagement start acme-corp 2026-q2
```
**Pre-condition:** Brand profile must exist at `~/.claude-marketing/brands/{brand-slug}/profile.json`. If not, run `/digital-marketing-pro:brand-setup` first.
**Checkpointing & resume:** The full checkpoint protocol — open a run on `start`, save each part as it completes, run `/digital-marketing-pro:check --full` before the Part 5 and Part 8 deliverables, then publish and finalize at the end — lives in the skill. See [engagement-workflow/SKILL.md](../skills/engagement-workflow/SKILL.md) § *Checkpointing & Resume* (the single source of truth). Each part's checkpoint saves **that part's own deliverable path** (Part 3 saves the Four Core Documents, Part 8 saves the Growth Plan — never a placeholder for a different part). An interrupted run resumes with `/digital-marketing-pro:resume`, and the finished files land in the visible output folder (`/digital-marketing-pro:output-folder {brand}`).
### `/digital-marketing-pro:engagement status [brand-slug] [engagement-id]`
Show the current engagement status. If brand and id are omitted, shows all active engagements.
**Example:**
```
/digital-marketing-pro:engagement status acme-corp 2026-q2
```
### `/digital-marketing-pro:engagement next [brand-slug] [engagement-id]`
Advance to the next part after confirming current is complete. Will not auto-advance — asks for confirmation.
### `/digital-marketing-pro:engagement validate <brand-slug> <engagement-id>`
Run Part 5 Client Validation. Invokes the `client-validation-document` skill to produce the deliverable. Pre-condition: Parts 2, 3, 4 must be complete.
### `/digital-marketing-pro:engagement re-run-decision <brand-slug> <engagement-id>`
Apply the Decision Matrix to determine which v2 re-runs are needed. Reads the Part 5 Client Validation responses and computes the re-run plan.
**Pre-condition:** Part 5 Client Validation responses must be saved at `engagements/{id}/part-05-client-validation/client-validation-responses.json`.
### `/digital-marketing-pro:engagement update-back <brand-slug> <engagement-id> --doc <doc-id> --reason "<reason>"`
Apply the Update-Back Rule (Part 7+ corrections). Bumps a source document version, saves new file, updates the Living Project Instruction File.
**Example:**
```
/digital-marketing-pro:engagement update-back acme-corp 2026-q2 --doc 3.1 --reason "Segment X CAC corrected from INR 3,000 to INR 4,800 based on Q2 channel data"
```
### `/digital-marketing-pro:engagement lif-show <brand-slug> <engagement-id>`
Display the Living Project Instruction File (the engagement's "currently true" record).
### `/digital-marketing-pro:engagement file-tree <brand-slug> <engagement-id>`
Show the engagement directory file tree.
### `/digital-marketing-pro:engagement list-engagements [brand-slug]`
List all engagements (optionally filtered by brand).
### `/digital-marketing-pro:engagement four-core <brand-slug> <engagement-id> [--doc 3.X] [--view v2] [--combined]`
Produce the Four Core Documents (Part 3). Shorthand for invoking the `four-core-documents` skill. Flags: `--doc` (single id `3.1` or comma-separated `"3.1,3.3"`), `--view v2` (Part 6 re-runs), `--combined` (stitch all four into the 3.C executive reference).
### `/digital-marketing-pro:engagement growth-plan <brand-slug> <engagement-id>`
Produce the Growth Plan (Part 8). Shorthand for invoking the `growth-plan` skill.
### `/digital-marketing-pro:engagement yearly-planner <brand-slug> <engagement-id>`
Produce the Yearly Planner (Part 8 companion). Shorthand for invoking the `yearly-planner` skill.
### `/digital-marketing-pro:engagement loop <brand-slug> <engagement-id>`
Produce a Part 12 Continuous Improvement deliverable (quarterly brief or ad-hoc). Shorthand for invoking the `continuous-improvement-loop` skill.
## Typical Engagement Flow
A complete engagement runs through these commands over weeks to months:
```
# Day 1: Setup
/digital-marketing-pro:brand-setup acme-corp # Creates brand profile (one-time per brand)
/digital-marketing-pro:engagement start acme-corp 2026-q2 # Initialises engagement; walks Part 1 intake
# Days 2-7: Unbiased research (Parts 2-4)
# (delegated to existing skills: market-intelligence, competitor-analysis, audience-intelligence)
/digital-marketing-pro:engagement next acme-corp 2026-q2 # Advance to Part 2 after Part 1 complete
# ... repeat advancement after each part
# Day 8: Strategic core (Part 3)
/digital-marketing-pro:engagement four-core acme-corp 2026-q2 # Produces all 4 core documents (61 steps)
# Day 14: Client validation (Part 5)
/digital-marketing-pro:engagement validate acme-corp 2026-q2 # Produces client validation document
# ... client reviews; responses captured in client-validation-responses.json
# Day 17: V2 re-runs (Part 6)
/digital-marketing-pro:engagement re-run-decision acme-corp 2026-q2 # Computes re-run plan
/digital-marketing-pro:engagement four-core acme-corp 2026-q2 --view v2 --doc 3.3 # Re-run specific docs as v2
# Days 18-21: Preparation + flagship deliverables (Parts 7-8)
/digital-marketing-pro:engagement next acme-Invoke when the user needs to manage multiple client brands, view portfolio-level dashboards, generate client reports, manage SOPs, switch credential profiles, assign team tasks, configure regions, or generate executive summaries. Triggers on requests involving multi-client management, agency workflows, client onboarding, or portfolio oversight.
Invoke when the user needs help with marketing measurement, KPI definition, dashboard design, attribution reporting, performance analysis, competitive benchmarking, or translating data into marketing decisions. Triggers on requests involving metrics, reporting, analytics setup, or data interpretation.
Invoke when marketing content needs quality control review — brand voice consistency checks, regulatory compliance verification (GDPR, CAN-SPAM, CCPA, HIPAA, FTC, industry-specific), accessibility auditing (WCAG 2.2), inclusive language review, or brand safety assessment. Automatically invoked as a final review step before any content is published or delivered.
Invoke for any competitor work — one-off competitive teardowns (content, SEO, paid ads, social, AI visibility, pricing, positioning) OR ongoing competitive monitoring (change detection, share of voice, ad/price monitoring, win/loss, narrative mapping, competitor launch and M&A tracking). Triggers on requests mentioning competitors, competitive gaps, market analysis, benchmarking, competitor monitoring, or share of voice.
Use when the task requires ongoing competitive monitoring, competitor change detection, share of voice tracking, competitive alerts, ad monitoring, price monitoring, win/loss analysis, or competitive narrative mapping.
Invoke when the user needs any form of marketing content created or refined — blog posts, ad copy, email campaigns, social media posts, landing page copy, press releases, video scripts, product descriptions, or newsletter content. Triggers on requests to write, draft, rewrite, or improve marketing copy.
Invoke when the user needs to manage CRM operations — creating contacts, importing leads, updating deals, syncing campaign data, segmenting audiences, managing pipelines, or connecting marketing data to Salesforce, HubSpot, Zoho, or Pipedrive. Triggers on requests involving CRM data, lead management, pipeline updates, or sales-marketing alignment.
Invoke when the user needs help with conversion rate optimization — landing page audits, A/B test design, form optimization, pricing page strategy, checkout flow improvement, personalization, statistical significance calculations, page speed impact analysis, or mobile conversion optimization. Triggers on requests involving conversions, landing pages, A/B testing, or optimization experiments.