teachskillofskills-ai/digitalmarketingpro-techshu/client-validation-document
Claude Code and agent skill by teachskillofskills-ai/digitalmarketingpro-techshu
- community
Checking that the SKILL.md file is still in the repository.
Produce the Part 5 Client Validation Document — the one true stop of the 12-Part engagement where unbiased v1 findings from Parts 2-4 are compiled into 12-25 evidence-cited finding blocks, each awaiting an ACCEPT / REJECT / EDIT / DEFER client decision, plus a paired JSON response template. Recorded responses feed the Part 6 Decision Matrix (engagement-state.py) to determine v2 re-runs. Triggers on \"/digital-marketing-pro:client-validation-document\", \"prepare v1 findings for client review\", \"run part 5 client validation\", \"the one true stop\", \"record the client's validation responses\". Requires Parts 3-4 marked completed in _engagement.json; reads the eight v1 core documents; pairs with /digital-marketing-pro:engagement-workflow and /digital-marketing-pro:four-core-documents.
Install
npx vskill@latest install teachskillofskills-ai/digitalmarketingpro-techshu/client-validation-documentSKILL.md
The same SKILL.md was published earlier as indranilbanerjee/digital-marketing-pro/client-validation-document.
/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:
- Parts 2, 3, 4 must be completed (or substantially complete with explicit acknowledgment that some research continues)
- The engagement state file
_engagement.jsonmust show Parts 3 and 4 ascompleted - 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:
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 tactical execution but not strategic direction. May or may not trigger re-runs.
- Low — accepting vs rejecting changes phrasing or examples but not substance. No re-run triggered.
The client should focus most attention on High materiality findings; Medium and Low are still presented for completeness.
Response Categorisation for the Decision Matrix
After the client provides responses, the responses are categorised into Decision Matrix triggers:
| Client decision pattern | Decision Matrix trigger | |
|---|---|---|
| Any competitor finding REJECTED or EDITED with new competitors | competitors_changed | |
| Any market sizing finding REJECTED or EDITED | target_market_changed | |
| Any segmentation finding REJECTED or EDITED with persona changes | audiences_changed | |
| Any positioning finding REJECTED or EDITED | positioning_changed | |
| Any budget / scope finding REJECTED or EDITED | budget_or_scope_changed | |
| Any pricing or offering finding REJECTED or EDITED | pricing_or_offering_changed | |
| Any unit economics finding REJECTED or EDITED | unit_economics_changed | |
| Only Low-materiality EDITs / minor wording corrections | minor_corrections_only |
The skill compiles the trigger list and runs:
The output then feeds the Part 6 v2 re-run plan.
Production Steps
- Verify pre-conditions — Parts 2, 3, 4 completed.
- Read the v1 source documents:
part-03-four-core-documents/v1/3.1-business-and-sbu-analysis.mdpart-03-four-core-documents/v1/3.2-segmentation-framework.mdpart-03-four-core-documents/v1/3.3-brand-positioning-and-communications.mdpart-03-four-core-documents/v1/3.4-dmflow.mdpart-04-competitive-customer-market/v1/4.1-competitor-ad-analysis.mdpart-04-competitive-customer-market/v1/4.2-competitor-positioning.mdpart-04-competitive-customer-market/v1/4.3-customer-analysis.mdpart-04-competitive-customer-market/v1/4.4-market-analysis.md
- Extract material findings. For each source document, identify the 2–5 most strategically consequential findings. Materiality rating: prefer High and Medium; include Low only if the client specifically benefits from confirming.
- Synthesise findings into the structured format. Use plain client-facing language, not internal jargon. Each finding stands alone — do not require the client to read the source documents.
- Add Open Questions section drawn from the "Open questions" sections of each source document.
- Add response mechanism section — instruct the client how to return responses (recommended: produce a paired
client-validation-responses.jsonfile alongside the document).
- Save the document to:
`` engagements/{id}/part-05-client-validation/client-validation-document.md ``
- Generate the response template:
`` engagements/{id}/part-05-client-validation/client-validation-responses.template.json `` Containing one entry per finding with empty decision/correction fields.
- Mark Part 5 as `awaiting_input` in
_engagement.json(notcompleted— Part 5 is only complete when the client responses are recorded).
- Brief the user on the document, the response mechanism, and the typical 7–14 day decision window.
Recording Client Responses
When the client returns responses (filled-in JSON file or verbal walkthrough captured in a meeting):
- Save the populated response file to:
`` engagements/{id}/part-05-client-validation/client-validation-responses.json ``
- Run
engagement-state.py decision-matrix --validation-file <path>to determine the v2 re-run plan.
- Mark Part 5 as
completed.
- Advance to Part 6 (v2 re-runs).
Quality Discipline
- Plain client language. No "MQL/SQL pipeline funnel architecture" jargon. Translate to "the way leads move from interested to ready-to-buy."
- Each finding stands alone. Client should not need to consult the source docs to understand the finding.
- Evidence is cited explicitly. Vague claims ("market data shows...") are unacceptable. Cite the specific source with the data point.
- Materiality is honest. Don't downgrade an uncomfortable finding to "Low" to make it easier to accept.
- Open Questions are real questions. Don't fabricate questions for the sake of having an Open Questions section.
- The response mechanism is structured. Free-form client emails are hard to translate into Decision Matrix triggers; the JSON response template makes the pattern unambiguous.
Examples
Example 1: Producing the document
Example 2: Recording client responses
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/client-validation-document/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/teachskillofskills-ai/digitalmarketingpro-techshu/client-validation-document)