engagement

# /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 (v3.7.7+):** After validating the pre-condition, the `start` subcommand opens a checkpoint run so an interruption mid-engagement can be resumed instead of restarted:

```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/checkpoint-manager.py init \
    --brand "{brand_slug}" --workflow engagement --topic "{engagement_id}"
```

The returned `run_id` is recorded in `_engagement.json` so subsequent `next` / `four-core` / `validate` / etc. subcommands can save their part outputs to the right run.

### Checkpointing — required for resumable engagement runs (v3.7.7+)

After each part completes (and passes its quality gate), the part owner saves its output:

```bash
# Part 1 (after stone-vs-opinion intake completes):
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/checkpoint-manager.py save \
    --brand "{brand}" --run-id "{run_id}" \
    --step 1 --content-file "{path_to_part1_deliverable}" --extension md

# Part 3 (after Four Core Documents):
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/checkpoint-manager.py save \
    --brand "{brand}" --run-id "{run_id}" \
    --step 3 --content-file "{path_to_growth_plan}" --extension md

# ...repeat for each part as it completes
```

If the run is interrupted (context exhaustion, user cancel, machine sleep), the user can resume with `/digital-marketing-pro:resume` — that command reloads every saved part and continues from the next un-checkpointed part. **This is the direct fix for the user-team feedback that "dm pro also taking too long to process"** — the workflow itself is not faster, but a single interruption no longer means losing 30+ minutes of work.

After the final part (Part 12 activation), publish every artifact to the user-visible output folder:

```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/output-publisher.py publish-run \
    --brand "{brand}" --run-id "{run_id}"

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/checkpoint-manager.py finalize \
    --brand "{brand}" --run-id "{run_id}" --status completed
```

Then point the user at the visible folder so they can find the 50-60 files:

```
✅ Engagement {engagement_id} complete for {brand}.

   📂 All deliverables are at:
      ~/Documents/DigitalMarketingPro/{brand}/engagement/{YYYY-MM}/

   Open with /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]`

Produce the Four Core Documents (Part 3). Shorthand for invoking the `four-core-documents` skill.

### `/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 c