commit a46cae2de9b1b5525d2fbf13ab1e38cdc21c1d21 Author: Zhongwei Li Date: Sat Nov 29 18:31:22 2025 +0800 Initial commit diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..d8009ff --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,25 @@ +{ + "name": "product-led-growth", + "description": "Self-serve onboarding, PQL routing, and in-app experiment governance", + "version": "1.0.0", + "author": { + "name": "GTM Agents", + "email": "opensource@intentgpt.ai" + }, + "skills": [ + "./skills/onboarding-blueprint/SKILL.md", + "./skills/pql-framework/SKILL.md", + "./skills/in-app-messaging-kit/SKILL.md", + "./skills/usage-health-scorecard/SKILL.md" + ], + "agents": [ + "./agents/product-adoption-strategist.md", + "./agents/pql-ops-lead.md", + "./agents/usage-growth-scientist.md" + ], + "commands": [ + "./commands/design-onboarding-journey.md", + "./commands/operationalize-pql-routing.md", + "./commands/launch-in-app-experiments.md" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..3d3d961 --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# product-led-growth + +Self-serve onboarding, PQL routing, and in-app experiment governance diff --git a/agents/pql-ops-lead.md b/agents/pql-ops-lead.md new file mode 100644 index 0000000..c8137a9 --- /dev/null +++ b/agents/pql-ops-lead.md @@ -0,0 +1,27 @@ +--- +name: pql-ops-lead +description: Runs product-qualified lead (PQL) engines, routing, and revenue workflows. +model: sonnet +--- + +# PQL Ops Lead Agent + +## Responsibilities +- Define PQL/PQA scoring logic across usage, firmographic, and intent signals. +- Own routing workflows into CRM, PLG motions, or CS playbooks. +- Monitor backlog, SLAs, and conversion impact of product-sourced opportunities. +- Collaborate with sales, CS, and marketing on follow-up cadences and messaging. + +## Workflow +1. **Signal Inventory** – audit product telemetry, enrichment, and entitlement data. +2. **Scoring Design** – build tiered scoring + qualification criteria per persona. +3. **Routing & Automation** – configure CRM/CS tooling, alerts, and ownership rules. +4. **Performance Monitoring** – track conversion, speed-to-lead, and revenue impact. +5. **Optimization Loop** – iterate scoring, journeys, and enablement assets based on feedback. + +## Outputs +- PQL scoring framework with weights + thresholds. +- Routing playbook and automation specs. +- Weekly performance report with insights + action items. + +--- diff --git a/agents/product-adoption-strategist.md b/agents/product-adoption-strategist.md new file mode 100644 index 0000000..b4e083b --- /dev/null +++ b/agents/product-adoption-strategist.md @@ -0,0 +1,29 @@ +--- +name: product-adoption-strategist +description: Designs onboarding journeys, activation plays, and product education + loops. +model: sonnet +--- + + +# Product Adoption Strategist Agent + +## Responsibilities +- Map onboarding journeys for key personas, tiers, and product surfaces. +- Define activation milestones, aha moments, and success metrics. +- Coordinate experiments across in-app, email, and lifecycle channels. +- Package learnings into enablement kits for GTM, CS, and product teams. + +## Workflow +1. **Persona & Journey Mapping** – gather data on roles, goals, and friction points. +2. **Activation Framework** – define milestones, metrics, and instrumentation requirements. +3. **Experiment Planning** – prioritize onboarding tests with hypotheses + success criteria. +4. **Enablement Delivery** – create runbooks, messaging, and tutorial assets. +5. **Feedback Loop** – monitor performance, collect qualitative signals, update playbooks. + +## Outputs +- Onboarding blueprint with milestones, comms, and measurement plan. +- Test backlog with scoring, owners, and timelines. +- Enablement pack for CS/marketing with messaging and templates. + +--- diff --git a/agents/usage-growth-scientist.md b/agents/usage-growth-scientist.md new file mode 100644 index 0000000..028df8b --- /dev/null +++ b/agents/usage-growth-scientist.md @@ -0,0 +1,27 @@ +--- +name: usage-growth-scientist +description: Synthesizes product telemetry, cohorts, and experiments to grow self-serve revenue. +model: haiku +--- + +# Usage Growth Scientist Agent + +## Responsibilities +- Analyze usage patterns, cohort retention, and monetization triggers. +- Identify segments for expansion plays, nudges, and usage-based upsells. +- Design and evaluate in-product experiments that drive activation → conversion. +- Share actionable insights with product, growth, and customer teams. + +## Workflow +1. **Data Wrangling** – unify telemetry, billing, and CRM data with consistent keys. +2. **Cohort Diagnostics** – examine activation, expansion, and churn by persona/product. +3. **Opportunity Modeling** – quantify lift potential for nudges, paywall tweaks, or pricing tests. +4. **Experiment Guidance** – recommend experiment design, guardrails, and measurement. +5. **Insight Sync** – publish readouts, playbooks, and follow-up experiment briefs. + +## Outputs +- Cohort + usage dashboards with prioritized opportunities. +- Experiment proposals with projected impact and measurement plan. +- Monthly insight digest with next-best-actions per segment. + +--- diff --git a/commands/design-onboarding-journey.md b/commands/design-onboarding-journey.md new file mode 100644 index 0000000..48fef9b --- /dev/null +++ b/commands/design-onboarding-journey.md @@ -0,0 +1,34 @@ +--- +name: design-onboarding-journey +description: Builds persona-specific onboarding journeys with milestones, messaging, and measurement. +usage: /product-led-growth:design-onboarding-journey --persona "Admin" --tier enterprise --channels in-app,email --window 30d +--- + +# Command: design-onboarding-journey + +## Inputs +- **persona** – target persona or job-to-be-done (Admin, IC, Exec, Developer). +- **tier** – plan/tier focus (free, pro, enterprise, beta). +- **channels** – comma-separated channels (in-app, email, chat, docs). +- **window** – onboarding time horizon (7d, 14d, 30d, custom). +- **metrics** – optional activation KPIs to emphasize. + +## Workflow +1. **Signal Review** – pull activation metrics, qualitative feedback, and experiment data. +2. **Milestone Mapping** – define aha moments, success metrics, and instrumentation requirements. +3. **Journey Blueprint** – lay out steps, channel mix, triggers, and dynamic variants. +4. **Enablement Pack** – create messaging, tutorials, and support resources. +5. **Measurement Plan** – document KPIs, guardrails, and reporting cadence. + +## Outputs +- Journey blueprint (diagram + table) with steps, channels, triggers. +- Content/messaging kit aligned to persona + milestones. +- Measurement + experiment plan with owners and timelines. + +## Agent/Skill Invocations +- `product-adoption-strategist` – architect journey + enablement. +- `usage-growth-scientist` – supplies activation data + experiment ideas. +- `onboarding-blueprint` skill – enforces structure + templates. +- `in-app-messaging-kit` skill – populates message library. + +--- diff --git a/commands/launch-in-app-experiments.md b/commands/launch-in-app-experiments.md new file mode 100644 index 0000000..50f31a5 --- /dev/null +++ b/commands/launch-in-app-experiments.md @@ -0,0 +1,35 @@ +--- +name: launch-in-app-experiments +description: Coordinates in-app experiments targeting activation, expansion, or monetization. +usage: /product-led-growth:launch-in-app-experiments --surface dashboard --goal activation --variants 3 --guardrails churn,latency +--- + +# Command: launch-in-app-experiments + +## Inputs +- **surface** – product area (dashboard, onboarding, billing, collaboration, mobile). +- **goal** – activation | engagement | monetization | retention. +- **variants** – number of experiment arms (including control). +- **guardrails** – comma-separated guardrail metrics to monitor. +- **audience** – persona/segment targeting (role, plan, region, cohort). +- **notes** – optional context or risk flags. + +## Workflow +1. **Hypothesis Intake** – capture hypotheses, prior learnings, and success metrics. +2. **Design Package** – define variant specs, targeting, triggers, and messaging. +3. **Instrumentation & Guardrails** – ensure events, tracking, and guardrails are wired. +4. **Launch & Monitoring** – deploy experiment, monitor metrics, trigger alerts. +5. **Readout Prep** – summarize results, decisions, and follow-up actions. + +## Outputs +- Experiment brief with hypotheses, variants, and instrumentation checklist. +- Guardrail + monitoring dashboard snapshot. +- Readout template with decision + rollout recommendation. + +## Agent/Skill Invocations +- `usage-growth-scientist` – leads experiment design + analysis. +- `product-adoption-strategist` – ensures journey alignment + messaging. +- `in-app-messaging-kit` skill – generates variant messaging + prompts. +- `usage-health-scorecard` skill – monitors guardrails + success metrics. + +--- diff --git a/commands/operationalize-pql-routing.md b/commands/operationalize-pql-routing.md new file mode 100644 index 0000000..19ea22b --- /dev/null +++ b/commands/operationalize-pql-routing.md @@ -0,0 +1,34 @@ +--- +name: operationalize-pql-routing +description: Builds scoring, routing, and follow-up workflows for product-qualified leads. +usage: /product-led-growth:operationalize-pql-routing --segment startup --threshold 80 --destinations crm,cs --alerts true +--- + +# Command: operationalize-pql-routing + +## Inputs +- **segment** – cohort focus (startup, scaleup, enterprise, education, region). +- **threshold** – minimum PQL/PQA score for routing. +- **destinations** – systems/teams to notify (crm, cs, marketing, product-qualified team). +- **playbook** – optional follow-up play (upsell, adoption, expansion, churn-save). +- **alerts** – true/false to include Slack/email alerts for SLA breaches. + +## Workflow +1. **Signal Review** – evaluate telemetry, entitlement, and intent fields for the segment. +2. **Scoring Model** – configure scoring weights, decay rules, and enrichment mapping. +3. **Routing Map** – define ownership, queue priority, and automation triggers. +4. **Playbook Assembly** – package messaging, assets, and SLAs for each destination. +5. **Monitoring Hooks** – establish dashboards + alerts for backlog, conversion, and SLA adherence. + +## Outputs +- PQL scoring + routing spec (JSON/CSV + narrative). +- Automation checklist for CRM/CS/rev tools. +- Follow-up playbook with sequences, assets, and owners. + +## Agent/Skill Invocations +- `pql-ops-lead` – owns scoring design + routing automation. +- `product-adoption-strategist` – ensures messaging + enablement align to journey. +- `pql-framework` skill – standardizes scoring methodology. +- `usage-health-scorecard` skill – monitors conversion + health metrics. + +--- diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..5cd5bdd --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,81 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:gtmagents/gtm-agents:plugins/product-led-growth", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "ae69241e3d9159a902fa45e2a3b3320edd7d24bb", + "treeHash": "bdb1036fa29c905da87fc8adc2475b4d9bace90c2a3129c9d2c955fd65a36aee", + "generatedAt": "2025-11-28T10:17:15.238056Z", + "toolVersion": "publish_plugins.py@0.2.0" + }, + "origin": { + "remote": "git@github.com:zhongweili/42plugin-data.git", + "branch": "master", + "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390", + "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data" + }, + "manifest": { + "name": "product-led-growth", + "description": "Self-serve onboarding, PQL routing, and in-app experiment governance", + "version": "1.0.0" + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "fcbec586c9df7e656c6e834b3a74ee1bd8170824c670e272a0fa16337204976a" + }, + { + "path": "agents/usage-growth-scientist.md", + "sha256": "859cfb647a9aa95bd6b4272b6f52c86db8bae9b1667b8d5031ae55b71cd3e29d" + }, + { + "path": "agents/pql-ops-lead.md", + "sha256": "19a2186ff8211fc81fe9229e4e82233f54b7f58be17ef583e4b14ec9d13dc484" + }, + { + "path": "agents/product-adoption-strategist.md", + "sha256": "e44dff66a4a7df90070f6c735e047b548d7f9fb92c435b8c0edb2d613965fbb1" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "1a8c70a25c8704388c8209ea04934deb420171b888be2601fef402a251b924f7" + }, + { + "path": "commands/design-onboarding-journey.md", + "sha256": "a953fa0222b740923578dd86ed4e1e667844946a3f4da5e76d300ceb3239d554" + }, + { + "path": "commands/operationalize-pql-routing.md", + "sha256": "4333513b890534af7507eb73f69dbd78e19cbba4f38ec3e6a9c04062fcf105b5" + }, + { + "path": "commands/launch-in-app-experiments.md", + "sha256": "6351df586437706e1a72ffc082c2dbc733f8aff20bedcbb7adc0d2f74b61e62f" + }, + { + "path": "skills/pql-framework/SKILL.md", + "sha256": "98611effc0c4d51eaef322d0214c6a778ed320ce4915ae0e95a377052f49fcb1" + }, + { + "path": "skills/in-app-messaging-kit/SKILL.md", + "sha256": "99019f176996fa0caf7c4ca864f3d4d3ad7d424c59caad71b694b1de00730d4c" + }, + { + "path": "skills/onboarding-blueprint/SKILL.md", + "sha256": "6e6bba35ad472f427176e4b791b2a13e8e553ddc6b433b2edfc23d163a3a101f" + }, + { + "path": "skills/usage-health-scorecard/SKILL.md", + "sha256": "f0baa575e49638f9fcd3c8f05cf656c7cd42e21da36136081f723d48feb2a5b9" + } + ], + "dirSha256": "bdb1036fa29c905da87fc8adc2475b4d9bace90c2a3129c9d2c955fd65a36aee" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file diff --git a/skills/in-app-messaging-kit/SKILL.md b/skills/in-app-messaging-kit/SKILL.md new file mode 100644 index 0000000..84f08af --- /dev/null +++ b/skills/in-app-messaging-kit/SKILL.md @@ -0,0 +1,30 @@ +--- +name: in-app-messaging-kit +description: Library of in-product message patterns, triggers, and targeting rules. +--- + +# In-App Messaging Kit Skill + +## When to Use +- Designing nudges, tooltips, and walkthroughs for onboarding or feature launches. +- Coordinating lifecycle messaging across in-app surfaces, chat, and email. +- Testing personalization ideas tied to usage milestones or cohorts. + +## Framework +1. **Trigger Matrix** – event-based, state-based, and contextual triggers. +2. **Message Patterns** – tooltip, modal, checklist, banner, coachmark, chat prompt. +3. **Targeting Rules** – persona, plan/tier, usage depth, lifecycle stage. +4. **Measurement Plan** – success metrics (CTR, completion, conversion) and guardrails. +5. **Localization + Accessibility** – copy guidelines, fallback flows, and escalation options. + +## Templates +- Message brief (goal, trigger, variant, CTA, measurement). +- Component library reference with best practices. +- Experiment tracker linking messages to outcomes. + +## Tips +- Keep copy concise; pair visuals or GIFs where possible. +- Schedule “quiet hours” to avoid notification overload. +- Tie each message to a single next-best-action to reduce decision fatigue. + +--- diff --git a/skills/onboarding-blueprint/SKILL.md b/skills/onboarding-blueprint/SKILL.md new file mode 100644 index 0000000..9f6a497 --- /dev/null +++ b/skills/onboarding-blueprint/SKILL.md @@ -0,0 +1,31 @@ +--- +name: onboarding-blueprint +description: Template for designing onboarding journeys, milestones, and measurement + plans. +--- + +# Onboarding Blueprint Skill + +## When to Use +- Creating persona-based onboarding for new tiers or product lines. +- Refreshing onboarding journeys after major product changes. +- Aligning product, CS, and marketing on activation milestones. + +## Framework +1. **Persona Canvas** – goals, motivations, blockers, success definition. +2. **Milestone Ladder** – aha moment, activation, stickiness, expansion triggers. +3. **Channel Mix** – in-app, email, docs, community, human assist with triggers. +4. **Instrumentation** – required events, metrics, and guardrails. +5. **Experiment Hooks** – backlog of tests tied to each milestone. + +## Templates +- Journey table (step, trigger, message, owner, metric). +- Metric dashboard layout for activation + retention. +- Experiment backlog sheet linked to milestones. + +## Tips +- Keep journeys lightweight; aim for 3-5 key milestones per persona. +- Combine qualitative inputs (surveys, interviews) with telemetry for context. +- Pair with `design-onboarding-journey` to auto-generate tailored blueprints. + +--- diff --git a/skills/pql-framework/SKILL.md b/skills/pql-framework/SKILL.md new file mode 100644 index 0000000..fcf1339 --- /dev/null +++ b/skills/pql-framework/SKILL.md @@ -0,0 +1,31 @@ +--- +name: pql-framework +description: Methodology for defining product-qualified lead (PQL) signals, scoring, + and routing. +--- + +# PQL Framework Skill + +## When to Use +- Standing up or recalibrating PQL/PQA programs. +- Aligning product, growth, and sales on what constitutes a high-intent product user. +- Auditing the health of existing PQL scoring + routing logic. + +## Framework +1. **Signal Library** – catalog feature usage, plan limits, collaboration signals, intent, firmographics. +2. **Scoring Model** – weight signals, set decay rules, and define negative indicators. +3. **Tiering** – map PQL tiers (A/B/C) to follow-up motions and SLAs. +4. **Routing Rules** – specify owners, cues, channels (CRM tasks, Slack alerts, CS queue). +5. **Measurement Loop** – track conversion, ARR impact, and feedback for model tuning. + +## Templates +- Signal inventory worksheet with data source + freshness. +- Scoring matrix with weights, thresholds, and decay logic. +- Routing decision tree linking tiers to plays. + +## Tips +- Start with simple tiering, iterate once telemetry + feedback improve. +- Include “disqualifier” signals (expired trials, churn risk) to avoid noise. +- Pair with `operationalize-pql-routing` to push models into automation. + +--- diff --git a/skills/usage-health-scorecard/SKILL.md b/skills/usage-health-scorecard/SKILL.md new file mode 100644 index 0000000..f3c983e --- /dev/null +++ b/skills/usage-health-scorecard/SKILL.md @@ -0,0 +1,30 @@ +--- +name: usage-health-scorecard +description: Framework for monitoring activation, engagement, and monetization guardrails. +--- + +# Usage Health Scorecard Skill + +## When to Use +- Tracking activation/retention metrics for self-serve and hybrid customer cohorts. +- Monitoring the impact of PLG experiments on core product health. +- Sharing health snapshots with product, growth, and CS leads. + +## Framework +1. **Metric Groups** – activation, engagement, collaboration, monetization, support load. +2. **Segmentation** – persona, plan, cohort, region, product area. +3. **Thresholds** – traffic light ranges for each metric with warning/critical bands. +4. **Alerting** – notification rules for drops, anomalies, or experiment impacts. +5. **Action Registry** – log remediation steps, owners, due dates, and results. + +## Templates +- Scorecard layout (metric, current, target, delta, owner). +- Dashboard wireframe with spark lines + annotations. +- Action tracker for follow-up tasks linked to health changes. + +## Tips +- Pair with `launch-in-app-experiments` to watch guardrails post-launch. +- Include qualitative signals (support tags, NPS) to contextualize telemetry. +- Archive snapshots to tell longitudinal stories in QBRs. + +---