digital-marketing-pro

Digital Marketing Pro — Claude Code & Cowork Plugin

The most comprehensive digital marketing plugin for Claude Code and Claude Cowork. v3.2 closes the v3.1 hook-removal gaps with /digital-marketing-pro:check (explicit pre-publish gate replacing the global PreToolUse hook), /digital-marketing-pro:status (richer on-demand brand snapshot replacing the global SessionStart banner), embedded mandatory hallucination check inside content-creator/email-specialist/social-media-manager/pr-outreach agents, opt-in auto_save_insights brand flag for ambient learning capture, and a documented hook re-enable pattern at the user's own settings level. v3.0 introduced the 12-Part Engagement Methodology — a sequential workflow that produces ~50–60 canonical files per engagement: Stone-vs-Opinion intake, unbiased external research, the Four Core Documents (61 explicit steps), Client Validation Document with Decision Matrix for v2 re-runs, the Update-Back Rule for in-life corrections, the Living Project Instruction File, the Growth Plan + Yearly Planner client deliverables, channel strategy fan-out, execution artefacts, AI creative instructions, and a continuous improvement loop that feeds back into product/offering decisions. Built on top of v2.7's foundation: 25 specialist agents, 149 skills, 68 Python scripts, 14 HTTP MCP connectors, 16 industry profiles, 16 privacy-law jurisdictions, and full execution-layer support.

---

v3.0 — The 12-Part Engagement Methodology

Most marketing tools generate isolated outputs — a campaign brief here, an email there, a content piece somewhere else. There is no canonical sequence, no shared state, no enforced structure. The result: inconsistent depth, missed dependencies, and outputs that do not compound across engagements.

v3.0 introduces a methodology-driven engagement workflow that fixes this. Every brand engagement now runs through the same 12 parts in sequence, producing the same set of files in the same order, with explicit dependency rules between them.

The 12 Parts at a Glance

Part	Name	Output
1	Client Inputs	Stone vs Opinion intake (what client knows for certain vs what they believe)
2	External Research	Unbiased market research (no client docs used)
3	Four Core Documents	61 explicit steps across Business & SBU Analysis (18), Segmentation Framework (15), Brand Positioning & Communications (19), DMFlow (9)
4	Competitive + Customer + Market	4 unbiased analysis documents (4.1–4.4)
5	Client Validation Document	The one true stop. Client accepts/rejects/edits each finding
6	Selective v2 Re-runs	Subset of Part 3 + Part 4 docs re-run per the Decision Matrix
7	Preparation Documents	Internal operating layer (campaign architecture, KPI tree, content pillars, asset inventory, approval chains)
8	Growth Plan + Yearly Planner	The flagship 11-section client-facing strategy + 12-month operational calendar
9	Channel Strategy Fan-out	Up to 17 channel docs grouped into 7 families (Search & Campaign, Paid platforms, Organic & Influencer, Marketplace & CRM, Content/ATL/BTL/PR, Web + Measurement)
10	Execution Artefacts	Communication outputs (ad copy, post copy, headlines, CTAs)
11	AI Creative Instructions	Visual asset briefs
12	Continuous Improvement Loop	Quarterly briefs + ad-hoc briefs feeding market + operating signals back into product/offering decisions

Key Architectural Concepts

• Two-Views Model — After Part 5, every engagement carries both v1 (the unbiased market view) and v2 (the client-validated view). Operating decisions reference v2; ideation and stress-testing reference both. v1 is never deleted.
• Stone vs Opinion — Every fact captured at intake is tagged with confidence level. Stone = client knows for certain. Opinion = client believes (becomes a research question, not ground truth).
• Decision Matrix — Maps client validation responses to which v1 documents need v2 re-runs. Prevents over- and under-re-running.
• Update-Back Rule — When live operations surface corrections after Part 7, the source documents get versioned (v2.1, v2.2 etc.) and the Living Project Instruction File propagates the change to all downstream skills.
• Living Project Instruction File — Single source of truth per engagement. All skills read it first. Auto-updated when source docs change.