/client-validation-document
Produce the Part 5 Client Validation Document — the one true stop where unbiased v1 findings meet the client. Each finding gets ACCEPT/REJECT/EDIT/DEFER decision.
$ npx -y skills add indranilbanerjee/digital-marketing-pro --skill client-validation-document --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/client-validation-document
Context preview
The summary Claude sees to decide when to auto-load this skill.
Produce the Part 5 Client Validation Document — the one true stop where unbiased v1 findings meet the client. Each finding gets ACCEPT/REJECT/EDIT/DEFER decision.
SKILL.md
client-validation-document.SKILL.mdname: client-validation-document
description: "Produce the Part 5 Client Validation Document — the one true stop where unbiased v1 findings meet the client. Each finding gets ACCEPT/REJECT/EDIT/DEFER decision."
user-invocable: true
triggers:
- produce client validation document
- run part 5 client validation
- prepare findings for client review
- client validation deliverable
- the one true stop
- prepare v1 findings for client
allowed-tools: Read Write Edit Bash Glob Grep
engagement-part: "5"
view-preference: v1-only
/digital-marketing-pro:client-validation-document — Part 5: The One True Stop
This skill produces the Part 5 deliverable: the Client Validation Document. It is the only point in the engagement where unbiased v1 findings are formally presented to the client for accept/reject/edit decisions.
Context efficiency
Heavy skill. **Grep before Read** any referenced file, then `Read` only matched ranges with `offset` + `limit`. List `${CLAUDE_PLUGIN_DATA}/<brand>/` before opening files. On re-invocation mid-session, skip files already in context.
This is the **one true stop** in the 12-Part flow. Nothing in Parts 6+ proceeds until this is signed off.
What this document is
The Client Validation Document compiles the most strategically consequential findings from Parts 2, 3, and 4 (the unbiased research and the four core documents) into a structured review document. For each finding:
- The finding itself
- Evidence / sources
- Proposed implication if accepted
- Three response options for the client: ACCEPT / REJECT / EDIT / DEFER
- (For REJECT or EDIT) — the client provides their corrected version and the rationale
The client's responses then feed the Decision Matrix in Part 6 to determine which v2 re-runs are needed.
What this document is NOT
- **Not a Growth Plan.** This is research findings, not strategic recommendations dressed up. The Growth Plan is Part 8.
- **Not exhaustive.** It includes only findings that have material strategic implications. Detail belongs in the source documents.
- **Not a slide deck.** It is a written document the client reads carefully and responds to. Slides do not capture the rigor required.
- **Not optional.** Every engagement runs Part 5. No shortcut to Part 6 without it.
Pre-conditions
Before running this skill:
1. Parts 2, 3, 4 must be completed (or substantially complete with explicit acknowledgment that some research continues) 2. The engagement state file `_engagement.json` must show Parts 3 and 4 as `completed` 3. The Living Project Instruction File should be up to date with the v1 strategic facts
If pre-conditions fail, do NOT produce output. Instruct the user on what is missing.
Document Structure
The Client Validation Document is organised by category of finding. Each category has 3–8 findings; total document is typically 12–25 findings across categories.
Section 1: Executive Briefing
**Length:** 1 page.
**Content:**
- Purpose of this document
- How to read it (the ACCEPT / REJECT / EDIT / DEFER framework)
- What happens after the client responds (Part 6 v2 re-runs governed by the Decision Matrix)
- Decision deadline (typically 7–14 days)
Section 2: Findings — by category
Each category contains its findings as structured blocks. Categories:
A. Business & SBU Findings (from 3.1)
Findings about the business reality — SBU separation, unit economics, value chain, growth levers, constraints, risks. Typically 3–5 findings.
B. Audience & Segmentation Findings (from 3.2 + 4.3)
Findings about target groups, persona priority, decision-making units, MQL/SQL definitions. Typically 3–5 findings.
C. Positioning & Communications Findings (from 3.3)
The chosen positioning, messaging pillars, tone-of-voice, don't-say rules, sensitive-topic handling. Typically 3–5 findings.
D. Channel & Budget Findings (from 3.4)
Channel selections, in-market vs out-market split, budget allocation, channel sequencing. Typically 2–4 findings.
E. Competitive Findings (from 4.1 + 4.2)
Competitor list, competitive positioning, Three-Question outputs (do well / do poorly / not doing). Typically 2–4 findings.
F. Market & Customer Findings (from 4.3 + 4.4)
Market sizing, customer behaviour patterns, demand signals. Typically 2–4 findings.
Section 3: Open Questions
Questions that the unbiased research could not resolve and need client input. The client provides answers here.
Section 4: Response Mechanism
How the client returns their responses (typically a structured response file or a meeting walkthrough).
Finding Block Format
Each finding follows this exact structure:
### Finding {ID}: {Short title}
**Category:** {A/B/C/D/E/F}
**Source:** {Document and step references — e.g., "3.1 Step 4, 4.1 Three-Question Output"}
**Materiality:** {High / Medium / Low}
**Finding:**
{2–4 sentences stating the finding from the unbiased research}
**Evidence:**
- {Cited source 1 with specific data point}
- {Cited source 2}
- {Cited source 3}
**Proposed implication if accepted:**
{1–3 sentences on what this means for the strategy if the client accepts}
**Client response:**
- [ ] ACCEPT — finding is correct as stated
- [ ] REJECT — finding is wrong; correction below
- [ ] EDIT — finding is partially correct; amended version below
- [ ] DEFER — needs further investigation; reason below
**If REJECT or EDIT, client correction:**
{Client fills in: what the correct finding is, with their evidence}
**If DEFER, reason and follow-up plan:**
{Client fills in: what additional research / data is needed, who is accountable, deadline}Materiality Classification
Each finding gets a Materiality rating that indicates how consequential the response is:
- **High** — accepting vs rejecting would meaningfully change the channel mix, budget, positioning, or audience priority. Triggers v2 re-runs per Decision Matrix.
- **Medium** — accepting vs rejecting would change tact
Read more
name: client-validation-document description: "Produce the Part 5 Client Validation Document — the one true stop where unbiased v1 findings meet the client. Each finding gets ACCEPT/REJECT/EDIT/DEFER decision." user-invocable: true triggers: - produce client validation document - run part 5 client validation - prepare findings for client review - client validation deliverable - the one true stop - prepare v1 findings for client allowed-tools: Read Write Edit Bash Glob Grep engagement-part: "5" view-preference: v1-only
/digital-marketing-pro:client-validation-document — Part 5: The One True Stop
This skill produces the Part 5 deliverable: the Client Validation Document. It is the only point in the engagement where unbiased v1 findings are formally presented to the client for accept/reject/edit decisions.
Context efficiency
Heavy skill. **Grep before Read** any referenced file, then `Read` only matched ranges with `offset` + `limit`. List `${CLAUDE_PLUGIN_DATA}/<brand>/` before opening files. On re-invocation mid-session, skip files already in context.
This is the **one true stop** in the 12-Part flow. Nothing in Parts 6+ proceeds until this is signed off.
What this document is
The Client Validation Document compiles the most strategically consequential findings from Parts 2, 3, and 4 (the unbiased research and the four core documents) into a structured review document. For each finding:
- The finding itself
- Evidence / sources
- Proposed implication if accepted
- Three response options for the client: ACCEPT / REJECT / EDIT / DEFER
- (For REJECT or EDIT) — the client provides their corrected version and the rationale
The client's responses then feed the Decision Matrix in Part 6 to determine which v2 re-runs are needed.
What this document is NOT
- **Not a Growth Plan.** This is research findings, not strategic recommendations dressed up. The Growth Plan is Part 8.
- **Not exhaustive.** It includes only findings that have material strategic implications. Detail belongs in the source documents.
- **Not a slide deck.** It is a written document the client reads carefully and responds to. Slides do not capture the rigor required.
- **Not optional.** Every engagement runs Part 5. No shortcut to Part 6 without it.
Pre-conditions
Before running this skill:
1. Parts 2, 3, 4 must be completed (or substantially complete with explicit acknowledgment that some research continues) 2. The engagement state file `_engagement.json` must show Parts 3 and 4 as `completed` 3. The Living Project Instruction File should be up to date with the v1 strategic facts
If pre-conditions fail, do NOT produce output. Instruct the user on what is missing.
Document Structure
The Client Validation Document is organised by category of finding. Each category has 3–8 findings; total document is typically 12–25 findings across categories.
Section 1: Executive Briefing
**Length:** 1 page.
**Content:**
- Purpose of this document
- How to read it (the ACCEPT / REJECT / EDIT / DEFER framework)
- What happens after the client responds (Part 6 v2 re-runs governed by the Decision Matrix)
- Decision deadline (typically 7–14 days)
Section 2: Findings — by category
Each category contains its findings as structured blocks. Categories:
A. Business & SBU Findings (from 3.1)
Findings about the business reality — SBU separation, unit economics, value chain, growth levers, constraints, risks. Typically 3–5 findings.
B. Audience & Segmentation Findings (from 3.2 + 4.3)
Findings about target groups, persona priority, decision-making units, MQL/SQL definitions. Typically 3–5 findings.
C. Positioning & Communications Findings (from 3.3)
The chosen positioning, messaging pillars, tone-of-voice, don't-say rules, sensitive-topic handling. Typically 3–5 findings.
D. Channel & Budget Findings (from 3.4)
Channel selections, in-market vs out-market split, budget allocation, channel sequencing. Typically 2–4 findings.
E. Competitive Findings (from 4.1 + 4.2)
Competitor list, competitive positioning, Three-Question outputs (do well / do poorly / not doing). Typically 2–4 findings.
F. Market & Customer Findings (from 4.3 + 4.4)
Market sizing, customer behaviour patterns, demand signals. Typically 2–4 findings.
Section 3: Open Questions
Questions that the unbiased research could not resolve and need client input. The client provides answers here.
Section 4: Response Mechanism
How the client returns their responses (typically a structured response file or a meeting walkthrough).
Finding Block Format
Each finding follows this exact structure:
### Finding {ID}: {Short title}
**Category:** {A/B/C/D/E/F}
**Source:** {Document and step references — e.g., "3.1 Step 4, 4.1 Three-Question Output"}
**Materiality:** {High / Medium / Low}
**Finding:**
{2–4 sentences stating the finding from the unbiased research}
**Evidence:**
- {Cited source 1 with specific data point}
- {Cited source 2}
- {Cited source 3}
**Proposed implication if accepted:**
{1–3 sentences on what this means for the strategy if the client accepts}
**Client response:**
- [ ] ACCEPT — finding is correct as stated
- [ ] REJECT — finding is wrong; correction below
- [ ] EDIT — finding is partially correct; amended version below
- [ ] DEFER — needs further investigation; reason below
**If REJECT or EDIT, client correction:**
{Client fills in: what the correct finding is, with their evidence}
**If DEFER, reason and follow-up plan:**
{Client fills in: what additional research / data is needed, who is accountable, deadline}Materiality Classification
Each finding gets a Materiality rating that indicates how consequential the response is:
- **High** — accepting vs rejecting would meaningfully change the channel mix, budget, positioning, or audience priority. Triggers v2 re-runs per Decision Matrix.
- **Medium** — accepting vs rejecting would change tact
Your agency just signed a 50-brand client. The previous agency left no playbook. Three brands are bleeding budget, two have stale positioning, one is launching in a regulated jurisdiction next month. Where do you start?
Other skills on digital-marketing-pro.
- /ab-test-plan
Design A/B and multivariate tests. Use when: sample size calculation, testing hypothesis, CRO experimentation.
Open skill - /ad-creative
Generate platform-specific ad copy. Use when: Google RSA, Meta, LinkedIn, TikTok ad variations with quality scoring.
Open skill - /add-integration
Add MCP server integrations. Use when: connecting a custom tool, API, or service to the plugin via .mcp.json.
Open skill - /aeo-audit
Audit AI search visibility. Use when: checking brand presence in ChatGPT, Perplexity, AI Overviews, Gemini.
Open skill - /aeo-geo
Optimize AI engine visibility. Use when: AEO/GEO strategy, citation optimization, entity consistency across AI platforms.
Open skill - /agency-dashboard
Portfolio-level agency dashboard aggregating health metrics across all client brands — campaign status, budget pacing, KPI attainment, team utilization. Use when reviewing cross-brand portfolio health, preparing for agency leadership standups, or getting a single-view snapshot
Open skill

