Files
skills/commands/plan-okrs.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

3.6 KiB

description, argument-hint, source
description argument-hint source
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results <team, product area, or company objective> phuryn/pm-skills

/plan-okrs -- Team OKR Planning

Generate well-structured OKRs that connect team work to company strategy. Produces 3 OKR sets with qualitative objectives and quantitative key results.

Invocation

/plan-okrs Growth team Q2 — company goal is 50% ARR increase
/plan-okrs Onboarding squad aligned to "improve activation rate"
/plan-okrs [upload company OKRs or strategy doc]

Workflow

Step 1: Gather Context

Ask the user:

  • What team or product area are these OKRs for?
  • What time period? (quarterly is standard, but could be annual or custom)
  • What are the company-level objectives these should ladder up to?
  • What happened last quarter? (hits, misses, learnings)
  • Any constraints or known priorities?

Accept company OKRs or strategy documents as uploads.

Step 2: Generate OKRs

Apply the brainstorm-okrs skill:

  • Create 3 OKR sets (Objective + 3-5 Key Results each)
  • Objectives: Qualitative, inspiring, ambitious but achievable, action-oriented
  • Key Results: Quantitative, measurable, time-bound, have clear owners
  • Ensure OKRs ladder to company objectives with visible connection
  • Balance leading indicators (activity) with lagging indicators (outcomes)

Step 3: Validate Quality

Check each OKR against best practices:

  • Is the Objective inspiring? (Would you rally a team around it?)
  • Are Key Results measurable? (Can you check completion with data, not judgment?)
  • Are targets ambitious but not demoralizing? (70% achievement = well-calibrated)
  • Are there 3-5 KRs per Objective? (More = unfocused)
  • Do KRs avoid gaming? (e.g., "ship 5 features" incentivizes shipping junk)

Flag any issues and suggest improvements.

Step 4: Present and Iterate

## Team OKRs: [Team Name] — [Period]

**Aligned to**: [Company Objective(s)]

### Objective 1: [Inspiring qualitative statement]
| # | Key Result | Baseline | Target | Owner |
|---|-----------|----------|--------|-------|
| KR1 | [measurable result] | [current] | [target] | [team/person] |
| KR2 | ... | ... | ... | ... |
| KR3 | ... | ... | ... | ... |

### Objective 2: [Inspiring qualitative statement]
[same format]

### Objective 3: [Inspiring qualitative statement]
[same format]

### Alignment Map
Company Objective → Team Objective → Key Results → Expected Impact

### Scoring Guide
- 0.0-0.3: Significant miss — investigate and learn
- 0.4-0.6: Progress made but fell short
- 0.7-0.9: Well-calibrated stretch goal — this is the target zone
- 1.0: Either nailed it or target wasn't ambitious enough

### Check-in Cadence
- **Weekly**: Quick traffic-light update on each KR
- **Mid-quarter**: Deep review, adjust targets if context changed
- **End of quarter**: Score, reflect, feed into next quarter

Offer:

  • "Want me to adjust ambition levels — make them more/less aggressive?"
  • "Should I create a metrics dashboard for tracking these?"
  • "Want me to draft a stakeholder update introducing these OKRs?"

Notes

  • OKRs should describe outcomes, not outputs ("Increase activation by 20%" not "Ship onboarding redesign")
  • If the user doesn't have company OKRs, help them derive team objectives from product strategy or business goals
  • Maximum 3 objectives per team per quarter — more means less focus
  • Key Results should be stretch goals — if you're certain you'll hit them, they're not ambitious enough
  • Flag any KR that could be gamed and suggest a counter-metric