Files
skills/public/product-strategy.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.7 KiB

name, description, source
name description source
product-strategy Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction. phuryn/pm-skills

Product Strategy Canvas

Metadata

  • Name: product-strategy
  • Description: Generate a comprehensive product strategy using the 9-section Product Strategy Canvas. Covers vision, market segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.
  • Triggers: product strategy, strategy canvas, strategic plan, product strategy document

Instructions

You are an experienced product strategist developing a comprehensive product strategy for $ARGUMENTS.

Your task is to create a detailed Product Strategy Canvas that outlines how the product will compete, win, and grow in the market.

Input Requirements

  • Product description and current positioning
  • Market context, competitors, and customer insights
  • Company resources, constraints, and priorities
  • Any relevant business or market data

Product Strategy Canvas Template

1. Vision

  • How can we inspire people?
  • What are we aspiring to achieve?
  • What values do we uphold?

2. Market Segments

  • Market defined by people's problems (not demographics)
  • Jobs to Be Done (JTBD), desired outcomes, constraints
  • Who is our first segment?
  • Why this segment first?

3. Relative Costs

  • Do we optimize for low cost (like Southwest Airlines)?
  • Or do we emphasize unique value (like Starbucks)?
  • What's our cost position relative to competitors?

4. Value Proposition

For each target segment:

  • What before: The customer's current situation, pain, or need
  • How: How your product delivers the solution
  • What after: The improved outcome or future state
  • Alternatives: What customers use today instead

5. Trade-offs

  • What will we NOT do?
  • What features or markets are out of scope?
  • How does saying "no" create focus and amplify our value?

6. Key Metrics

  • North Star Metric: Single metric that drives overall business success
  • OMTM (One Metric That Matters): The one metric we optimize for this quarter

7. Growth

  • Sales-Led Growth or Product-Led Growth?
  • Primary acquisition channels
  • How do we scale?
  • What's our unit economics?

8. Capabilities

  • What competencies and resources do we need?
  • What do we build vs. partner for?
  • What capabilities must we develop to win?

9. Can't/Won't

  • Why can't competitors easily copy this?
  • What defensibility do we have (network effects, switching costs, IP)?
  • What barriers to entry exist for new competitors?

Output Process

  1. Define the vision and aspirational impact
  2. Identify 2-3 target market segments with their JTBD
  3. Establish cost positioning (low cost vs. premium value)
  4. Develop value propositions for each segment
  5. List explicit trade-offs (what we won't do)
  6. Set North Star and quarterly OMTM
  7. Outline growth strategy and channels
  8. Document required capabilities and partnerships
  9. Explain defensibility and barriers to competition
  10. Validate strategy coherence: ensure elements reinforce each other
  11. Surface critical hypotheses that must be true for success
  12. Suggest low-effort experiments to test key assumptions

Notes

  • Ensure all 9 elements fit together logically
  • Identify what must be true for this strategy to work (hypotheses)
  • Propose validation experiments with minimal effort
  • Strategy guides decisions; clarity enables faster execution
  • Revisit quarterly as market conditions change

Templates


Further Reading