Files
skills/commands/discover.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.8 KiB
Raw Permalink Blame History

description, argument-hint, source
description argument-hint source
Run a full product discovery cycle — from ideation through assumption mapping to experiment design <product or feature idea> phuryn/pm-skills

/discover -- Full Discovery Cycle

Run a structured product discovery process that moves from divergent thinking to focused validation. This command chains multiple skills into a single end-to-end workflow.

Invocation

/discover Smart notification system for our project management tool
/discover New product: AI writing assistant for non-native speakers
/discover                    # asks what you're discovering

Workflow

Step 1: Understand the Discovery Context

Determine whether this is:

  • Existing product — continuous discovery on a known product with real users
  • New product — initial discovery for a concept without validated demand

Ask the user:

  • What are you exploring? (product idea, feature area, opportunity space)
  • What do you already know? (prior research, customer feedback, data)
  • What decisions will this discovery inform? (build/kill, prioritize, pivot)

Accept context from uploaded files (research, PRDs, transcripts, data), links, or conversation.

Step 2: Brainstorm Ideas (Divergent Phase)

Apply the brainstorm-ideas-existing or brainstorm-ideas-new skill:

  • Generate ideas from PM, Designer, and Engineer perspectives
  • Present the top 10 ideas with brief rationale
  • Ask the user to select 3-5 ideas to carry forward, or accept all

Checkpoint: "Here are 10 ideas. Which ones should we stress-test? Pick 3-5, or I can carry all forward."

Step 3: Identify Assumptions (Critical Thinking Phase)

For each selected idea, apply the identify-assumptions-existing or identify-assumptions-new skill:

  • Surface assumptions across risk categories:
    • Value: Will users want this?
    • Usability: Can users figure it out?
    • Feasibility: Can we build it?
    • Viability: Does the business case work?
    • Go-to-Market (new products only): Can we reach and convert users?
  • Use devil's advocate multi-perspective analysis
  • Compile a master list of all assumptions across all ideas

Step 4: Prioritize Assumptions (Focus Phase)

Apply the prioritize-assumptions skill:

  • Map assumptions on an Impact × Risk matrix
  • Identify the "leap of faith" assumptions — high impact, high uncertainty
  • Rank assumptions by test priority
  • Group related assumptions that can be tested together

Checkpoint: "Here are your riskiest assumptions. Which ones feel most critical to validate first?"

Step 5: Design Experiments (Validation Phase)

For the top-priority assumptions, apply brainstorm-experiments-existing or brainstorm-experiments-new skill:

  • Design 1-2 experiments per critical assumption
  • For existing products: A/B tests, fake doors, prototypes, user tests, data analysis
  • For new products: XYZ hypotheses, pretotypes, landing pages, concierge MVPs
  • Include success criteria, timeline, and effort for each
  • Sequence experiments by dependency and effort

Step 6: Create Discovery Plan

Compile everything into a discovery plan document:

## Discovery Plan: [Topic]

**Date**: [today]
**Product Stage**: [existing/new]
**Discovery Question**: [what we're trying to learn]

### Ideas Explored
[Summary of brainstormed ideas with brief descriptions]

### Selected Ideas for Validation
[3-5 ideas carried forward with rationale]

### Critical Assumptions
| # | Assumption | Category | Impact | Uncertainty | Priority |
|---|-----------|----------|--------|-------------|----------|

### Validation Experiments
| # | Tests Assumption | Method | Success Criteria | Effort | Timeline |
|---|-----------------|--------|-----------------|--------|----------|

### Experiment Details
[For each experiment: hypothesis, setup, measurement, decision criteria]

### Discovery Timeline
Week 1: [experiments]
Week 2: [experiments]
Week 3: [analysis and decision]

### Decision Framework
- If [experiment] succeeds → proceed to [next step]
- If [experiment] fails → [pivot/kill/investigate further]

Save the plan as a markdown file to the user's workspace.

Step 7: Offer Next Steps

  • "Want me to create a PRD for the top idea?"
  • "Should I design an interview script to supplement these experiments?"
  • "Want me to set up metrics to track the experiments?"
  • "Should I estimate effort and create user stories for the MVP?"

Notes

  • This is a 15-30 minute structured workflow — let the user know upfront
  • At each checkpoint, the user can redirect, skip, or go deeper
  • If the user has research data, pull insights from it before brainstorming
  • The discovery plan should be a living document — offer to update it as experiments run
  • For new products, emphasize desirability validation before feasibility
  • For existing products, check if there's usage data that can inform assumptions