Organic Growth AdvisorSAFE
Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
Overview
Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
0b657a54b6d7OBSERVED · 2026-10-07What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: organic-growth-advisor argument-hint: "[product and growth context]" description: "Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next." intent: >- Guide product managers through a fast triage to identify which of four organic growth paths fits their current constraint: new customer segments (L2), new geographies (L3), new distribution channels (L4), or new products or services (L5). Uses a 2x2 diagnostic based on customer/market context familiarity and degree of product change required. Outputs a growth path recommendation with rationale and immediate next steps. type: interactive best_for: - "Choosing which organic growth motion to pursue when multiple seem viable" - "Diagnosing whether the constraint is in reach, access, market context, or product value" - "Setting up an AI-assisted growth experiment with the right starting hypothesis" scenarios: - "We need to grow but aren't sure if we should go after new customer segments or new geographies" - "Help me figure out which McKinsey growth level we should focus on" - "We have strong product-market fit but growth is stalling. Where should we look?" - "Which organic growth path fits our current situation?" theme: strategy-positioning estimated_time: "15-25 min" --- ## Purpose Help product managers identify which organic growth path to pursue by diagnosing where the constraint actually lives. This is not a comprehensive strategy tool. It is a fast triage that puts you in the right lane before you start building hypotheses or running experiments. The four growth paths covered here are drawn from the McKinsey Growth Pyramid (Levels 2 through 5). Levels 1, 6, and 7 are out of scope: Level 1 (existing products to existing customers) is a retention and optimization problem, not a growth motion. Levels 6 and 7 (new industry structure, new arenas) require capital and executive mandate beyond typical product team scope. This skill does three things and nothing more: 1. Diagnoses where your growth constraint lives using two questions 2. Places your situation on the Growth Path Matrix (customer/market context vs. degree of product change) 3. Recommends one growth path with rationale, a diagnostic question, and a first experiment ### Anti-Patterns (What This Is NOT) - **Not a rigorous diagnostic instrument:** A fast triage tool, not a scoring model - **Not a maturity model or rubric:** No stages, no grades, no weighted criteria - **Not a substitute for customer discovery:** It points you in a direction; discovery validates it - **Not a guarantee:** If the recommendation does not feel right, that tension is worth exploring ### When to Use This Skill - Growth is stalling and you are unsure which lever to pull next - Multiple growth paths seem viable and you need to choose one to test first - You want to set up an AI-assisted experiment with a clear hypothesis - A team or stakeholder debate about growth direction needs a fast resolution ### When NOT to Use This Skill - You have not yet achieved core product-market fit (fix L1 first) - You already have a validated growth path in motion (do not switch lanes mid-experiment) - You need a rigorous strategic planning tool (this is triage, not strategy) - You lack basic context about your current customers and their problems (gather that first) --- ## Input **Works best with:** Your product and where growth feels stuck, in a sentence or two. **Also useful:** Which customers/markets you serve today, what you've already tried, and any paths leadership is pushing (new segments, geos, channels, products). Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The advisor opens with Q1 of the 3-question triage to place you on the Growth Path Matrix. **Example invocation:** `Growth triage: B2B payroll tool, strong in US mid-market, plateaued — CEO wants Europe, sales wants an SMB tier.` ## Key Concepts ### The Growth Path Matrix Two questions place your situation on the matrix: **X axis: Customer/Market Context** How familiar is the next customer or market you want to reach? - **Known:** Same market, same type of buyer, familiar problem context - **Less Known:** Different geography, unfamiliar cultural or regulatory context, buyer type you have not served before **Y axis: Degree of Product Change** How much does the product itself need to change to unlock the next wave of growth? - **Low:** The product mostly works. What needs to change is how customers find or access it, or which customer you go after next. - **High:** The product needs to evolve. New capabilities or an entirely new product line is required to solve the next job. ### The Four Growth Paths **L2: New Customer Segments** (Known context + Low product change) You already solve a real problem. A nearby buyer may need it too. **L4: New Distribution Channels** (Known context + High product change) Product offers same value. People need a better way to find or access it. **L3: New Geographies** (Less Known context + Low product change) The product may travel. The market context does not come with it automatically. **L5: New Products or Services** (Less Known context + High product change) Customers are pulling you toward adjacent jobs your offer does not fully solve. ### Why This Order Matters Risk scales with distance from your core. L2 is closest: same market, same product. L5 is furthest: new product, less familiar context. Most teams overinvest in L5 before they have exhausted L2 and L4. If your core product-market fit is strong and your current market is not saturated, L2 or L4 is almost always the right move first. ### The Knowledge Principle Innovation at
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
0b657a54b6d7full audit observations/trust-audit/skill/deanpeters__organic-growth-advisor.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 0b657a54b6d7 | SAFE | B | 89 | first audit |
Questions
What does the Organic Growth Advisor skill do?
Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.
Is Organic Growth Advisor safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Organic Growth Advisor access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (0b657a54b6d7), read on 2026-10-07. The repository is watched, and a new audit runs when it changes — this is the first audit.