voc-dispatch

/voc-dispatch — Produce the Artifacts

/voc-route decides who needs to know. This skill writes the thing they receive. Every artifact must be openable on its own and make sense to someone who never read the synthesis.

Requires

What	Value
Input	outputs/voc/routed/*.md
Config	context/product-context.md for voice constraints and team names
Cost	Free.

Nothing here sends anything. Every artifact is a draft on disk. Sending is a human decision.

---

A. Case-study outreach email

For each entry in case-study-leads.md:

• 80-120 words, from a named human, not "the marketing team"
• Opens by referencing the specific outcome they described, in their words. This is the whole reason the pipeline preserved verbatim quotes through four stages.
• Asks for 30 minutes. One ask.
• No adjectives about your own product. They already bought it.
• If the routing entry has no specific outcome, hold the email and say so. Do not write a generic request and do not invent a result they did not claim.

→ outputs/voc/dispatched/case-study-emails/<customer>-<date>.md

B. Landing-page copy brief

For each objection in objection-map.md:

• The objection in prospect language, with mention count and channel spread
• The page or pages it should be addressed on
• Where on the page: hero, an FAQ entry, a comparison block, a dedicated section. An objection answered in the wrong place is answered too late.
• Two or three drafted options for the copy that addresses it
• What evidence the page needs to make it credible — a number, a customer name, a screenshot

Copy constraints, applied to everything drafted here: no em dashes, no "it's not X, it's Y", no more than two consecutive negations, no robust / seamless / powerful / enterprise-grade / best-in-class / effortless / game-changing. Write the benefit first and the feature second.

→ outputs/voc/dispatched/copy-briefs/<page-slug>-<date>.md

C. PM one-pager

For each capability area in product-feedback.md: