four-core-documents
Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4 DMFlow — with --doc single-document runs, --view v2 re-runs, and a --combined executive stitch.
Install / Use
npx skills add indranilbanerjee/digital-marketing-pro --skill four-core-documentsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of four-core-documents
four-core-documents scores 92/100 on our quality scale, 331st of 1,213 Content & Media skills we index (top 28%).
Its SKILL.md is 16 KB long, well organised into 32 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.
It has 832 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 26 days ago, so four-core-documents is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
four-core-documents compared with similar skills
All 4 of these similar skills score higher than four-core-documents; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| four-core-documents (this skill)by indranilbanerjee | 92 | 832 | 26d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 90.1k | 18d ago | CLAUDE.md |
| siyuanby siyuan-note | 100 | 46.6k | today | MCP Server |
| algorithmic-artby anthropics | 100 | 177.9k | 11d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install four-core-documents?
- Run
npx skills add indranilbanerjee/digital-marketing-pro --skill four-core-documents. The install tabs above show the steps for each supported agent. - Which AI agents does four-core-documents work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is four-core-documents safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is four-core-documents still maintained?
- The repository was last updated 26 days ago, so four-core-documents is actively maintained.
Skill content
View source on GitHubname: four-core-documents description: "Produce Part 3 of the 12-Part engagement: the four strategic-spine documents across 61 steps — 3.1 Business & SBU Analysis, 3.2 Segmentation Framework, 3.3 Brand Positioning & Communications, 3.4 DMFlow — with --doc single-document runs, --view v2 re-runs, and a --combined executive stitch. Triggers on "/digital-marketing-pro:four-core-documents", "produce the four core documents", "run part 3 of the engagement", "generate the strategic spine", "re-run positioning as v2". Requires an initialised engagement with Part 1 complete; reads Stone facts, Part 2 research, and the brand profile, and feeds /digital-marketing-pro:growth-plan." user-invocable: true allowed-tools: Read Write Edit Bash Glob Grep engagement-part: "3" view-preference: v2-primary
/digital-marketing-pro:four-core-documents — The Strategic Spine (61 Steps)
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.
Context efficiency
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.
Pre-conditions
Before running this skill, verify:
- Brand profile exists at
~/.claude-marketing/brands/{brand-slug}/profile.json. If not, run/digital-marketing-pro:brand-setupfirst. - Engagement is initialised with state file
_engagement.jsonpresent. If not, run/digital-marketing-pro:engagement startfirst. - Part 1 (Client Inputs) is completed. Stone facts and Opinion hypotheses must be captured before Part 3 can begin.
- Part 2 (External Research) is at least started. Some Part 2 research may continue in parallel with Part 3, but the kickoff must have happened.
If any pre-condition fails, do NOT produce output. Instead, instruct the user on what to run first.
Subcommands
Produce all four documents
/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.
Produce a single document
/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.
Produce v2 re-runs
/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.)
Produce the Combined Core Document (3.C)
/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.
Production Order
The four documents are produced in sequence because each builds on the prior:
- 3.1 Business & SBU Analysis (18 steps) — foundational. Establishes the business reality.
- 3.2 Segmentation Framework (15 steps) — depends on 3.1's SBU and customer data.
- 3.3 Brand Positioning & Communications (19 steps) — depends on 3.2's personas.
- 3.4 DMFlow (9 steps) — depends on 3.1, 3.2, and 3.3 to make channel decisions.
When running re-runs, only the affected documents are regenerated. Other documents remain at their current version.
Per-Document Production
3.1 — Business & SBU Analysis (18 steps)
Read the spec section for 3.1 in four-core-documents-spec.md. The 18 steps are:
- SBU identification
- SBU separation rationale
- Revenue streams per SBU
- Unit economics per SBU
- Value chain mapping
- Offering portfolio at task-level granularity
- Pricing architecture
- Organisational and go-to-market model
- Sales and distribution architecture
- Full SWOT with evidence
- Growth levers
- Constraints
- Customer acquisition economics
- Customer retention economics
- Partnership and channel dependencies
- Risk profile
- Strategic implications for the engagement
- Open questions
Inputs:
part-01-client-inputs/stone-facts.json— ground-truth factspart-02-external-research/— unbiased external research (industry data, market context)- Brand profile at
~/.claude-marketing/brands/{slug}/profile.json - (Do NOT use Opinion hypotheses as ground truth — those are research questions, not facts)
Output:
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.
3.2 — Segmentation Framework (15 steps)
The 15 steps:
- Target Group identification
- TG scoring across criteria
- TG prioritisation
- Sub-TG breakdown
- Persona development per primary TG (using actionable-persona-format.md)
- Behavioural attributes per persona
- Psychographic attributes per persona
- Need-state mapping
- Geographic distribution
- (B2B only) Multi-stakeholder Decision Unit per persona (using b2b-decision-making-unit.md)
- (B2B only) MQL definition
- (B2B only) SQL definition
- (B2B only) Pipeline logic
- Anti-personas
- 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:
- 3.1 (just produced) for SBU + customer baseline
part-04-competitive-customer-market/v1/4.3-customer-analysis.mdif available (for unbiased customer research)- Brand profile
Output:
engagements/{id}/part-03-four-core-documents/v1/3.2-segmentation-framework.md
3.3 — Brand Positioning & Communications (19 steps)
The 19 steps:
- Positioning options considered
- Per-option rationale
- Per-option trade-offs
- Chosen positioning with defence argument
- Positioning statement (formal one-sentence)
- Trade-offs explicit
- Brand promise
- Proof points for the brand promise
- Primary message architecture
- Messaging pillars (3–5)
- Proof points per pillar
- Segment-level messaging variations
- Full-funnel communication framework (TOFU/MOFU/BOFU/retention/advocacy)
- Tone-of-voice principles
- Explicit don't-say rules
- Sensitive-topic handling
- Crisis-communication posture
- Application guidance across channels
- Open positioning questions
Inputs:
- 3.1 + 3.2 (just produced)
part-04-competitive-customer-market/v1/4.2-competitor-positioning.mdif available- Brand profile (for current brand voice signals)
Output:
engagements/{id}/part-03-four-core-documents/v1/3.3-brand-positioning-and-communications.md
3.4 — DMFlow (9 steps)
The 9 steps:
- Channel universe considered (using five-digital-markets.md)
- Channel selection with rationale per channel
- Funnel architecture per channel
- Media mix logic across paid/organic/earned/owned
- Budget allocation logic at business level (with In-Market vs Out-Market split per in-market-out-market.md)
- Channel interdependencies and sequencing
- Conversion framework
- Measurement approach
- Strategic implications and track weightages
Inputs:
- 3.1 + 3.2 + 3.3 (just produced)
- Brand profile (for current channels, budget envelope)
- channel-families.md for the 7-family / 17-channel taxonomy
Output:
engagements/{id}/part-03-four-core-documents/v1/3.4-dmflow.md
Quality Discipline (Apply to All Four Documents)
- Every claim cites a source. No "we think" — only "the evidence shows" with cited source.
- Every assumption is explicit. When estimating CAC, LTV, market size, etc., state the methodology and inputs.
- Every recommendation flows from analysis. No conclusions the body does not support.
- No generic statements. "Strong brand" is generic. "92% brand recall in target segment per [source]" is specific.
- All four documents reference each other consistently. A persona defined in 3.2 must be the same persona referenced in 3.3 messaging variations and 3.4 channel selection.
- Open questions are documented, not hidden.
- Stone facts are facts; Opinion hypotheses are questions. Don't elevate Opinion to fact in the document.
- Multi-Dimensional Decision Framework (see decision-framework.md) is used for any choice (channel selection, persona prioritisation, positioning trade-offs).
Single-File Discipline
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:
- Save the partial document so far
- Continue the same file from where it left off in the next turn (NEVER start a new file)
- The file is considered complete only when all steps are present
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.
After Production
Once all four documents are produced (or after each individually):
- Update the Living Project Instruction File:
- Strategic Facts section: extract positioning statement, primary persona summary, channel selections, unit economics
- Version History section: add the new v1.0 entries
- Mark Part 3 (or the specific sub-document) as completed in
_engagement.json - Notify the user that Part 4 is the natural next step
v2 Re-runs
When invoked with --view v2, the skill:
- Reads the v1 version of the requested doc
- Reads the Part 5 Client Validation Document (the changes the client requested)
- Reads the relevant subset of changes that apply to this doc
- Produces v2 with a header section listing what changed vs v1:
## v1 → v2 Changes
- Section X (Step N): {what changed} — driven by {client validation finding ID}
- Section Y: ...
- Saves to
v2/{doc-name}.md(the
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
90.1kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
siyuan
46.6kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx 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 or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
