---
name: go-to-market
description: Develop or review product positioning, audience segmentation, launch strategy, channels, pricing or packaging implications, enablement, operational readiness, adoption measurement, and post-launch learning. Use for go-to-market plans, launch plans, messaging, audience strategy, sales or partner enablement, and launch readiness.
---

# Go to Market

Translate validated product value into a credible adoption and launch system. Do not manufacture market evidence or promise unavailable capabilities.

## Inputs

- target users, buyers, influencers, and blockers
- customer and market evidence
- product value, scenarios, differentiation, and limitations
- launch scope, availability, regions, pricing, packaging, and timing constraints
- channel, sales, partner, support, documentation, and operational capabilities
- success measures and business goals

## Workflow

When authoring or revising a document, draft its substance, then invoke the bundled `classic-style` skill before final validation. Request **keep my structure; output only**. Preserve the required template, claims, citations, uncertainty, decisions, and code examples; polish prose only. Keep style notes in chat, outside the document. If skill invocation is unavailable, read `../classic-style/SKILL.md` and its reference and apply them directly. If those files are unavailable, report the missing dependency and ask to repair the installation rather than silently skipping it.

1. Define the launch objective and audience segments.
2. Distinguish user, buyer, administrator, partner, and influencer needs.
3. Articulate the category, problem, value, differentiation, proof, and limitations.
4. Map the journey from awareness through evaluation, activation, adoption, retention, and advocacy.
5. Select channels and motions based on evidence and audience behavior.
6. Identify required content, demos, documentation, training, sales, partner, support, and community enablement.
7. Assess product, operational, legal, localization, support, and measurement readiness.
8. Define staged rollout, experiments, feedback loops, guardrails, and stop conditions.
9. Assign owners and dependencies.
10. Identify claims that require validation before external use.

## Output

### Launch objective and scope

### Audience and stakeholder segments

### Positioning and message architecture

Include category, problem, value proposition, differentiation, proof, objections, and limitations.

### Adoption journey and channels

### Launch plan and milestones

### Enablement and operational readiness

### Risks and mitigations

### Success, guardrail, and learning measures

### Readiness verdict

Ready | Ready with named blockers | Not ready | Insufficient evidence

## Quality bar

- Positioning traces to evidence and shipped or committed capabilities.
- Each audience receives a relevant outcome, proof point, and call to action.
- Launch readiness includes support, documentation, operations, and measurement.
- Measures cover adoption and sustained value, not only impressions or launch activity.
- Risks include owners, mitigations, and stop conditions.

## Boundaries

- Own launch and adoption strategy, not unilateral product scope changes.
- Do not publish, contact customers, set pricing, or make external commitments without explicit authority.
- Use `customer-discovery` when audience or message evidence is weak.
- Use `developer-experience-review` for developer-facing products.
- Escalate material claims or commitments to `product-ceo` and, when appropriate, `board-review`.