Produce the Four Core Documents at strategic depth (61 total steps): Business & SBU Analysis, Segmentation Framework, Brand Positioning, DMFlow. Use when running Part 3 of the engagement methodology.
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill four-core-documents
This skill produces Part 3 of the engagement methodology: the four documents that together define the brand at strategic depth. Every channel strategy, every creative brief, every piece of copy reads back to these.
Heavy skill. Grep before Read any referenced file, then Read only matched ranges with offset + limit. List the brand's workspace at ~/.claude-marketing/brands/{slug}/ (or $CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/ when that env var is set) before opening files. On re-invocation mid-session, skip files already in context.
Specification: four-core-documents-spec.md — the exact 61 steps across the four documents.
Engagement context: engagement-flow-methodology.md — where Part 3 fits in the 12-Part flow.
Before running this skill, verify:
~/.claude-marketing/brands/{brand-slug}/profile.json. If not, run /digital-marketing-pro:brand-setup first._engagement.json present. If not, run /digital-marketing-pro:engagement start first.If any pre-condition fails, do NOT produce output. Instead, instruct the user on what to run first.
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id>
Produces 3.1, 3.2, 3.3, 3.4 in sequence. Actual time varies with engagement complexity.
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id> --doc 3.1
Produces just the specified document. Useful for re-runs (Part 6) or when one doc needs to be redone independently.
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id> --view v2 --doc "3.1,3.3"
Produces v2 versions of the specified documents. --doc takes a single id (3.1) or a comma-separated list ("3.1,3.3"). Used during Part 6 after the Decision Matrix has triggered re-runs. (The canonical flags are --doc, --view v2, and --combined — there is no --docs.)
/digital-marketing-pro:four-core-documents <brand-slug> <engagement-id> --combined
Stitches all four canonical core documents (latest version of each) into a single executive-reference file with master TOC, master assumptions table, and master source index. Produced only when an executive audience needs a single-file read.
The four documents are produced in sequence because each builds on the prior:
When running re-runs, only the affected documents are regenerated. Other documents remain at their current version.
Read the spec section for 3.1 in four-core-documents-spec.md. The 18 steps are:
10. Full SWOT with evidence
11. Growth levers
12. Constraints
13. Customer acquisition economics
14. Customer retention economics
15. Partnership and channel dependencies
16. Risk profile
17. Strategic implications for the engagement
18. Open questions
Inputs:
part-01-client-inputs/stone-facts.json — ground-truth factspart-02-external-research/ — unbiased external research (industry data, market context)~/.claude-marketing/brands/{slug}/profile.jsonOutput:
engagements/{id}/part-03-four-core-documents/v1/3.1-business-and-sbu-analysis.md
(For v2 re-runs: same path but in v2/ instead of v1/)
Output structure:
---
document: 3.1-business-and-sbu-analysis
version: v1.0
engagement: {engagement-id}
brand: {brand-slug}
produced: {iso-timestamp}
view: v1 # or v2 for re-runs
---
# 3.1 Business & SBU Analysis
## Step 1: SBU Identification
[Content for step 1]
## Step 2: SBU Separation Rationale
[Content for step 2]
... (all 18 steps, in order)
## Sources
[Numbered list of every cited source: client docs, public sources, industry reports, Stone facts referenced]
## Open Questions
[Anything that could not be answered with available info]
## Change Log
### v1.0 — {date}
- Initial unbiased research version produced from Part 2 + Stone facts.
The 15 steps:
10. (B2B only) Multi-stakeholder Decision Unit per persona (using b2b-decision-making-unit.md)
11. (B2B only) MQL definition
12. (B2B only) SQL definition
13. (B2B only) Pipeline logic
14. Anti-personas
15. Activation guidance
Steps 10–13 are skipped for B2C engagements. The skill detects B2B vs B2C from the brand profile's business_model.type field.
Inputs:
part-04-competitive-customer-market/v1/4.3-customer-analysis.md if available (for unbiased customer research)Output:
engagements/{id}/part-03-four-core-documents/v1/3.2-segmentation-framework.md
The 19 steps:
10. Messaging pillars (3–5)
11. Proof points per pillar
12. Segment-level messaging variations
13. Full-funnel communication framework (TOFU/MOFU/BOFU/retention/advocacy)
14. Tone-of-voice principles
15. Explicit don't-say rules
16. Sensitive-topic handling
17. Crisis-communication posture
18. Application guidance across channels
19. Open positioning questions
Inputs:
part-04-competitive-customer-market/v1/4.2-competitor-positioning.md if availableOutput:
engagements/{id}/part-03-four-core-documents/v1/3.3-brand-positioning-and-communications.md
The 9 steps:
Inputs:
Output:
engagements/{id}/part-03-four-core-documents/v1/3.4-dmflow.md
Each document is produced as a single file containing all its steps. If a document cannot be completed in one turn due to output limits:
There is no hidden continuation state — the skill does not persist a cut-off pointer. The partial file already saved to disk is the only record. If output is interrupted mid-document, re-run the document: read the saved partial as context and continue appending the remaining steps to the same file. For a run interrupted at the engagement level, resume from the part's last checkpoint artifact via /digital-marketing-pro:resume. The saved file is always the source of truth.
Once all four documents are produced (or after each individually):
_engagement.jsonWhen invoked with --view v2, the skill:
## v1 → v2 Changes
- Section X (Step N): {what changed} — driven by {client validation finding ID}
- Section Y: ...
v2/{doc-name}.md (the v1 file remains untouched)_engagement.json via engagement-state.py bump-versionUser: Produce the four core documents for the Acme engagement.
Skill response:
1. Verify pre-conditions: brand profile ✓, engagement initialised ✓, Part 1 complete ✓, Part 2 in progress ✓
2. Begin 3.1 Business & SBU Analysis. Read Stone facts, Part 2 research, brand profile. Walk all 18 steps. Cite sources throughout. Save to v1/3.1-business-and-sbu-analysis.md.
3. Begin 3.2 Segmentation Framework. Read 3.1, Part 4.3 if available. Detect business model = B2B from profile, so include steps 10-13. Walk 15 steps. Save to v1/3.2-segmentation-framework.md.
4. Begin 3.3 Brand Positioning. Read 3.1, 3.2, Part 4.2 if available. Walk 19 steps. Save to v1/3.3-brand-positioning-and-communications.md.
5. Begin 3.4 DMFlow. Read 3.1, 3.2, 3.3. Apply 5 Digital Markets taxonomy. Walk 9 steps. Save to v1/3.4-dmflow.md.
6. Update LIF: positioning statement, primary persona, channel selections, blended CAC estimate.
7. Mark Part 3 completed.
8. Brief: "Part 3 complete. 4 documents, 61 steps. Total ~12,000 words across all four. Recommend reviewing 3.3 (positioning) carefully — the chosen positioning has notable trade-offs documented in step 6."
User: Re-run 3.3 and 3.4 as v2 — client rejected the positioning and we need to redo the channel mix as a result.
Skill response:
1. Verify Part 5 Client Validation Document exists with positioning rejection captured ✓
2. Begin 3.3 v2. Read 3.3 v1 + Client Validation Document. Re-do positioning per client direction. Add v1→v2 changes header. Save to v2/3.3-brand-positioning-and-communications.md.
3. Begin 3.4 v2. Read 3.4 v1 + (now updated) 3.3 v2. Re-do channel mix to align with new positioning. Add v1→v2 changes header. Save to v2/3.4-dmflow.md.
4. Bump versions: engagement-state.py bump-version --doc 3.3 + --doc 3.4
5. Update LIF: new positioning statement, new channel selections, version history.
6. Brief: "v2 re-runs complete. 3.1 and 3.2 unchanged (still v1.0). 3.3 and 3.4 now at v2.0. Both views remain available. Operating decisions should reference v2 docs."
User: Produce the Combined Core Document for the executive presentation next week.
Skill response:
1. Verify all four core documents exist (latest version of each) ✓
2. Read 3.1 v1.0, 3.2 v1.0, 3.3 v2.0, 3.4 v2.0
3. Synthesise into single document with:
- Master TOC at top
- Each document as a major section
- Master Assumptions Table (extract every "Assumption" call-out from all four docs)
- Master Source Index (de-duplicated list of every source cited)
4. Save to part-03-four-core-documents/3.C-combined-core-document.md
5. Brief: "3.C produced. 60+ pages. Includes master TOC + assumptions table + source index. Recommended exports: PDF for the executive deck, DOCX if they want to annotate."
engagement-workflow — orchestrates the 12-Part flow that contains Part 3client-validation-document — Part 5 deliverable that triggers v2 re-runsaudience-intelligence, competitive-intel, market-intelligence, brand-guardianComprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Take indranilbanerjee/four-core-documents from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.