Initial commit

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.
+
+---

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.
+
+---

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.
+
+---