Product-Led Media Map
Invoke as $product-led-media-map.
Report-First Approval Gate
Default to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.
Do not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write/update/fix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research/report writes.
When stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. Do not include Recommended next skill, Recommended next command, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.
Connect a product, company, or founder project to a credible creator-media strategy. This is for product-led media, not generic content marketing.
Evidence And Feedback Handling
Treat user feedback as input to evaluate, not as automatic ground truth.
- For factual, evidentiary, technical, or source-backed claims: verify against available evidence. If the user appears to misunderstand the evidence or states something factually incorrect, push back clearly and cite the evidence. Do not rewrite findings merely to agree.
- For taste, brand, positioning preference, risk appetite, prioritization, or other subjective judgment calls: weigh user feedback heavily and adapt the recommendation unless it conflicts with verified evidence.
- When feedback mixes facts and preference, separate them explicitly: correct the factual part, then incorporate the preference where it is a legitimate judgment call.
- When uncertain, say what is known, what is inferred, and what would change the conclusion.
Inputs
- Product context:
README.md, specs/**, research/**, docs, changelogs, demos, launch notes.
- Preferred creator context when present:
research/creator-presence/<slug>.md.
- Creator context:
research/youtube/creator-positioning-<slug>.md, channel audit, portfolio, and programming docs when present.
Output
Create the research/youtube/ directory if it does not exist.
Write research/youtube/product-led-media-map-<slug>.md with:
- Product truth: what can be shown, proven, or taught.
- Audience overlap: product users, buyers, community, and broader media audience.
- Proof assets: demos, workflows, customer language, benchmarks, build logs, failures, behind-the-scenes evidence.
- Media themes: education, build-in-public, market analysis, case studies, product demos, founder judgment.
- Trust risks: overpromising, thin proof, sensitive customer data, sponsor conflicts, product-market mismatch.
- Content-role mapping: acquisition, trust-building, proof, education, launch support, retention.
- Recommended links to
$content-programming and $series-spec.
Approved Artifact Handoff
After an approved synthesized write, explicit write/update mode, or any direct artifact mutation:
- List every created or updated synthesized artifact path in the final response.
- State the verification performed, such as readback, schema/check command, or why no executable verification applies for a Markdown-only strategy artifact.
- Check and report the relevant git status for intended artifacts when the project is a git repository. If intended artifacts are modified or untracked, make the next action shipping, committing, or an explicit dirty-artifact handoff before recommending downstream strategy work.
- Do not imply the research workflow is complete while approved artifacts remain untracked or uncommitted unless the user explicitly asked not to ship.
- If stopping for approval before writing, the approval request remains the next action; do not include downstream routing.
Intent-Aware Routing
Before applying the default ## Next-Skill Routing sequence, classify the user's immediate intent and route to the missing action that best serves that intent:
- Strategy refresh: recommend the missing or stale positioning, programming, portfolio, metrics, or product-media artifact.
- Recording prep: recommend the missing series spec, script, build proof, walkthrough guide, or validation artifact needed before recording.
- Upload prep: recommend packaging, title/thumbnail, description, chapters, or final metadata work before broader strategy work.
- Performance review: recommend metrics, cadence, portfolio, peer benchmark, or owner-analytics export work before new content planning.
- Owner analytics or private/manual platform evidence: route to an explicit manual/guide handoff instead of inventing unavailable metrics.
- Dirty intended artifacts: route to shipping/commit/handoff first, not another creator strategy skill.
Use the default next-skill sequence only when no stronger user intent, missing artifact, manual blocker, or dirty-artifact handoff applies.
Alignment Page
When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following ALIGNMENT-PAGE.md in this skill's directory. Output: alignment/product-led-media-map-{topic}.html.
Constraints
- Do not create product claims the repo cannot support.
- Do not expose secrets, private customer data, or unreleased commitments.
- Use the dossier when present to connect product proof to the creator's public roles and proof assets; do not require it for YouTube-only product-led channel work.
- Keep product-led media distinct from ad copy; show evidence and judgment.
1---2name: product-led-media-map-43description: Map a product or company into founder-led YouTube media themes, proof assets, demos, trust moments, and content roles4---5
6# Product-Led Media Map
7
8Invoke as `$product-led-media-map`.
9
10## Report-First Approval Gate
11
12Default to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.
13
14Do not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write/update/fix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research/report writes.
15
16When stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.
17
18Connect a product, company, or founder project to a credible creator-media strategy. This is for product-led media, not generic content marketing.
19
20## Evidence And Feedback Handling
21
22Treat user feedback as input to evaluate, not as automatic ground truth.
23
24- For factual, evidentiary, technical, or source-backed claims: verify against available evidence. If the user appears to misunderstand the evidence or states something factually incorrect, push back clearly and cite the evidence. Do not rewrite findings merely to agree.
25- For taste, brand, positioning preference, risk appetite, prioritization, or other subjective judgment calls: weigh user feedback heavily and adapt the recommendation unless it conflicts with verified evidence.
26- When feedback mixes facts and preference, separate them explicitly: correct the factual part, then incorporate the preference where it is a legitimate judgment call.
27- When uncertain, say what is known, what is inferred, and what would change the conclusion.
28
29## Inputs
30
31- Product context: `README.md`, `specs/**`, `research/**`, docs, changelogs, demos, launch notes.
32- Preferred creator context when present: `research/creator-presence/<slug>.md`.
33- Creator context: `research/youtube/creator-positioning-<slug>.md`, channel audit, portfolio, and programming docs when present.
34
35## Output
36
37Create the `research/youtube/` directory if it does not exist.
38
39Write `research/youtube/product-led-media-map-<slug>.md` with:
40
41- Product truth: what can be shown, proven, or taught.
42- Audience overlap: product users, buyers, community, and broader media audience.
43- Proof assets: demos, workflows, customer language, benchmarks, build logs, failures, behind-the-scenes evidence.
44- Media themes: education, build-in-public, market analysis, case studies, product demos, founder judgment.
45- Trust risks: overpromising, thin proof, sensitive customer data, sponsor conflicts, product-market mismatch.
46- Content-role mapping: acquisition, trust-building, proof, education, launch support, retention.
47- Recommended links to `$content-programming` and `$series-spec`.
48
49## Approved Artifact Handoff
50
51After an approved synthesized write, explicit write/update mode, or any direct artifact mutation:
52
53- List every created or updated synthesized artifact path in the final response.
54- State the verification performed, such as readback, schema/check command, or why no executable verification applies for a Markdown-only strategy artifact.
55- Check and report the relevant git status for intended artifacts when the project is a git repository. If intended artifacts are modified or untracked, make the next action shipping, committing, or an explicit dirty-artifact handoff before recommending downstream strategy work.
56- Do not imply the research workflow is complete while approved artifacts remain untracked or uncommitted unless the user explicitly asked not to ship.
57- If stopping for approval before writing, the approval request remains the next action; do not include downstream routing.
58
59## Intent-Aware Routing
60
61Before applying the default `## Next-Skill Routing` sequence, classify the user's immediate intent and route to the missing action that best serves that intent:
62
63- Strategy refresh: recommend the missing or stale positioning, programming, portfolio, metrics, or product-media artifact.
64- Recording prep: recommend the missing series spec, script, build proof, walkthrough guide, or validation artifact needed before recording.
65- Upload prep: recommend packaging, title/thumbnail, description, chapters, or final metadata work before broader strategy work.
66- Performance review: recommend metrics, cadence, portfolio, peer benchmark, or owner-analytics export work before new content planning.
67- Owner analytics or private/manual platform evidence: route to an explicit manual/guide handoff instead of inventing unavailable metrics.
68- Dirty intended artifacts: route to shipping/commit/handoff first, not another creator strategy skill.
69
70Use the default next-skill sequence only when no stronger user intent, missing artifact, manual blocker, or dirty-artifact handoff applies.
71
72## Alignment Page
73
74When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/product-led-media-map-{topic}.html`.
75
76## Constraints
77
78- Do not create product claims the repo cannot support.
79- Do not expose secrets, private customer data, or unreleased commitments.
80- Use the dossier when present to connect product proof to the creator's public roles and proof assets; do not require it for YouTube-only product-led channel work.
81- Keep product-led media distinct from ad copy; show evidence and judgment.
GeorgeQLe