client-validation-document

name	client-validation-document
description	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.
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.