Distribute: Go-To-Market Strategy

This skill turns a defined product into a Go-To-Market Strategy — a ranked pick of three distribution channels and, for each, a simple, specific, step-by-step plan to get started. It reads the Define work (ideally the synthesized PRODUCT.md) — or, in a repo without ProductOS, the codebase itself — then researches the actual places this product's customers already gather and how competitors in the category distribute, and walks the user through selecting channels and turning each into a concrete first-week runbook.

The goal is not to list channels. The goal is to make every step so specific to this product that it could not have been written for any other. "Post on Reddit" is worthless; "post your note-from-voice demo in r/therapists (220k) framed as 'I built this because writing progress notes after every session was eating my evenings'" is a plan. The difference between those two sentences is the entire value of this skill. A channel is only useful once it names the exact place, the exact first move in the customer's own words, and the exact number that means it's working.

The most common ways a first go-to-market fails are picking too many channels, picking the channel the founder enjoys instead of the one the customer is on, and writing a plan so generic it gives no actual instruction. This skill exists to prevent all three: it forces exactly three ranked channels with one crowned primary, anchors every pick to evidence of where the customer already is, and rewrites any step that would read the same for a different product.

Session length: Designed to be completable in 45–60 minutes of conversation. All channel research is Claude's job during the session — finding the named subreddits/Discords/hashtags/keywords/creators/marketplaces and the competitor-distribution teardown. The user reacts and supplies founder context (audience, budget, what they'll actually do); they do not go off and research channels. The skill identifies and fully plans all three channels — not just the primary — so the user (often with a coach in a 1:1 review) can decide where to start, with a real plan waiting for whichever channel they choose. When run in a repo without ProductOS, the skill first reads the codebase for product context and asks a few qualifying questions — the customer, where they gather, and the price — to stand in for the Define docs before the channel research begins.

Inputs

This skill needs three things: product context (what the product is, who it's for, how it makes money), an output target (where the strategy gets written), and the channel playbook (how to choose and run channels). Product context is gathered one of two ways — the standard path reads the ProductOS folder (productos/ at the app repo root, or the current folder in a standalone ProductOS checkout); the fallback covers a repo with no ProductOS at all — but the rest of the workflow is identical either way.

Product context — Path A (standard): ProductOS in the repo

Locate the Define work in the ProductOS folder — productos/ at the app repo root (or the current folder in a standalone ProductOS checkout):