Files
skills/commands/plan-launch.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

4.5 KiB

description, argument-hint, source
description argument-hint source
Create a full go-to-market strategy — beachhead segment, ICP, messaging, channels, and launch plan <product or feature to launch> phuryn/pm-skills

/plan-launch -- Go-to-Market Strategy

Build a complete GTM plan from first principles: identify your beachhead market, define the ideal customer, craft messaging, choose channels, and create a launch timeline.

Invocation

/plan-launch AI-powered proposal writer for consulting firms
/plan-launch New enterprise tier for our project management tool
/plan-launch [upload a PRD, strategy doc, or pitch deck]

Workflow

Step 1: Understand the Launch

Ask:

  • What are you launching? (new product, new feature, new tier, market expansion)
  • What stage? (pre-launch planning, imminent launch, post-launch optimization)
  • Do you have existing customers? Or starting from zero?
  • What's the timeline? Any hard deadlines?
  • Budget constraints? Team size?

Step 2: Define Beachhead Segment

Apply the beachhead-segment skill:

  • Evaluate potential market segments against:
    • Burning pain (how urgently they need this)
    • Willingness to pay (budget and purchase authority)
    • Winnable market share (can you reach and win them)
    • Referral potential (will they tell others)
  • Recommend the single best starting segment with rationale
  • Map adjacent segments for expansion after beachhead is secured

Step 3: Define Ideal Customer Profile

Apply the ideal-customer-profile skill:

  • Demographics: company size, industry, geography, tech stack
  • Behaviors: how they discover solutions, buying process, decision makers
  • JTBD: specific jobs they're hiring your product for
  • Current alternatives: what they use today and why it falls short
  • Qualification criteria: how to identify them quickly

Step 4: Build GTM Strategy

Apply the gtm-strategy skill:

  • Positioning: How you describe yourself to this segment
  • Messaging: Key messages for different stakeholders (buyer, user, influencer)
  • Channels: Where and how to reach your ICP (ranked by expected ROI)
  • Launch tactics: Specific actions for pre-launch, launch day, and post-launch
  • Pricing alignment: How pricing supports the GTM motion
  • Success metrics: How you'll know the launch worked

Step 5: Generate GTM Plan

## Go-to-Market Plan: [Product/Feature]

**Launch date**: [target]
**Type**: [new product / feature / tier / market expansion]

### Beachhead Segment
**Who**: [specific segment definition]
**Why them first**: [rationale against criteria]
**Size**: [TAM/SAM/SOM estimate]

### Ideal Customer Profile
| Attribute | Definition |
|-----------|-----------|
| Company size | [range] |
| Industry | [specific] |
| Decision maker | [title/role] |
| Key JTBD | [job they need done] |
| Current solution | [what they use today] |
| Qualification signal | [how to identify them] |

### Positioning & Messaging
**Positioning statement**: For [who] who [need], [product] is [category] that [benefit]. Unlike [alternative], we [differentiator].

**Key messages by stakeholder**:
| Audience | Message | Proof Point |
|----------|---------|------------|

### Channel Strategy
| Channel | Tactic | Reach | Cost | Priority |
|---------|--------|-------|------|----------|

### Launch Timeline
| Phase | Timing | Actions | Owner |
|-------|--------|---------|-------|
| Pre-launch | [dates] | [list] | [who] |
| Launch week | [dates] | [list] | [who] |
| Post-launch | [dates] | [list] | [who] |

### Success Metrics
| Metric | 30-day target | 90-day target |
|--------|-------------|-------------|

### Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|-----------|

### Expansion Plan
[After beachhead: which adjacent segments, in what order, with what adaptations]

Save as markdown.

Step 6: Offer Next Steps

  • "Want me to design growth loops for post-launch traction?"
  • "Should I create competitive battlecards for sales?"
  • "Want me to draft marketing copy for the launch?"
  • "Should I build a metrics dashboard for launch tracking?"

Notes

  • "Everyone" is not a segment — the tighter the beachhead, the faster you learn
  • The ICP should be specific enough that sales/marketing can identify prospects in 30 seconds
  • Messaging should use the customer's language, not your internal terminology
  • Pre-launch activities (waitlist, beta, early access) are as important as launch day
  • Plan for post-launch: the first 90 days after launch determine long-term trajectory