Craft Go-To-Market (GTM communication) v1 — English / US edition

New here, or not sure this is the right skill? Start right here — or run nmt-chat, describe your situation, and it points you to the right one. Quick map: new idea → nmt-market-research · live product or a metric moved → nmt-diagnose · have customer interviews → nmt-analyze-interviews · ready to build → nmt-product-requirements · positioning / launch copy → nmt-craft-value-proposition → nmt-craft-go-to-market.

One breath. This skill turns the value you've already built into the copy that brings in customers — landing copy, ad/creative copy, and a launch + growth plan. It's the last step of the chain and builds on the steps before it; it never invents the segment, the value, or the build. Everything is said through the bigger outcome the customer is really after (their Big Job, where motivation lives), in concrete, measurable terms (success criteria, not adjectives), with features used as proof, not as the message. Copy can carry value, not manufacture it: if the value isn't proven yet, the skill says so up front — it can still write you demand-test copy, just don't scale on it.

Producer contract (binding) — ../nmt-chat/references/producer-contract.md. Alongside the shared orientation, output, input-as-hypothesis, path, validation-debt, and Deep-mode rules, this skill keeps market and audience language conditional, permissioned repo-context reads, claim status/provenance, independent n/N source counts, single-signal handling, source-to-segment traceability, and input-sensitive confidence. GTM has no GO verdict — it inherits the debt of the value it sells.

Where this skill sits in the chain

nmt-market-research → nmt-craft-value-proposition → nmt-product-requirements → nmt-craft-go-to-market
(segment + Jobs)    (the value hypothesis)      (the build spec)         (THIS SKILL: the copy
                                                                          that sells the value)

It runs from a plain-English description of your product, your customer, and what you sell — that's a first-class way in, not a fallback. If you've already run an upstream skill, even better: it'll use a nmt-craft-value-proposition result (best — it carries the positioning headline, the dominant criteria, the moment it clicks for the customer (the Aha moment), the differentiation, the proof), a nmt-product-requirements PRD (the real functionality, the step-by-step path the customer walks (the Critical Chain of Jobs), where the Aha lands), or a nmt-market-research result (segment, Big/Core Jobs, competitors, the underserved angle you win on). Either way, it does not re-derive segments, re-invent value, or re-spec the build — it packages what you give it into customer-facing language. (One footer point only: copy can't prove value, so test the value before you scale spend — more below.)

What this skill produces