Initial commit

commands/launch-experiment.md

@@ -0,0 +1,35 @@
+---
+name: launch-experiment
+description: Converts an approved hypothesis into a fully-instrumented test with guardrails and rollout plan.
+usage: /growth-experiments:launch-experiment --id EXP-142 --surface onboarding --variant-count 3 --ramp 5,25,50,100
+---
+
+# Command: launch-experiment
+
+## Inputs
+- **id** – experiment or hypothesis identifier.
+- **surface** – product area/channel (onboarding, pricing page, lifecycle email, in-app).
+- **variant-count** – number of variants/arms including control.
+- **ramp** – comma-separated rollout schedule (%) or JSON file reference.
+- **holdout** – optional holdout/ghost-experiment definition for measurement.
+- **notes** – free-text for special approvals or exception handling.
+
+## Workflow
+1. **Readiness Check** – confirm design sign-off, instrumentation coverage, and guardrails.
+2. **Variant Assembly** – pull specs, assets, and targeting rules for each arm.
+3. **Rollout Plan** – configure flag/experimentation platform with ramp schedule + alerts.
+4. **QA & Approvals** – run smoke tests, capture screenshots, and gather stakeholder approval.
+5. **Launch & Monitoring** – activate test, enable telemetry dashboards, and notify channels.
+
+## Outputs
+- Launch packet with specs, QA evidence, approvals, and rollout timeline.
+- Experiment platform configuration export + guardrail monitors.
+- Stakeholder announcement + escalation matrix.
+
+## Agent/Skill Invocations
+- `test-engineer` – builds variants, instrumentation, and QA evidence.
+- `experimentation-strategist` – confirms governance + approvals.
+- `guardrail-scorecard` skill – validates guardrail coverage + thresholds.
+- `experiment-design-kit` skill – ensures templates + best practices are applied.
+
+---

commands/prioritize-hypotheses.md

@@ -0,0 +1,34 @@
+---
+name: prioritize-hypotheses
+description: Scores experiment backlog using impact, confidence, effort, and guardrail readiness.
+usage: /growth-experiments:prioritize-hypotheses --source backlog.csv --capacity 6 --framework rice
+---
+
+# Command: prioritize-hypotheses
+
+## Inputs
+- **source** – backlog file, experiment tracker, or Notion database ID.
+- **capacity** – number of experiments that can run in the next sprint/cycle.
+- **framework** – ice | rice | custom; determines scoring weights.
+- **guardrails** – optional JSON/CSV for mandatory guardrail requirements.
+- **filters** – tags or OKRs to focus on (acquisition, activation, retention, monetization).
+
+## Workflow
+1. **Data Ingestion** – load backlog, normalize fields, and enrich with latest metrics.
+2. **Scoring Engine** – calculate ICE/RICE/custom scores, factoring guardrail readiness.
+3. **Portfolio Mix** – ensure balance across funnel stages and surfaces; flag conflicts.
+4. **Capacity Planning** – fit highest-value tests into available slots, accounting for owners + effort.
+5. **Decision Pack** – generate prioritized list, rationale, and trade-off notes for approval.
+
+## Outputs
+- Ranked backlog with scores, dependencies, and guardrail status.
+- Capacity plan showing selected tests plus waitlist.
+- Decision memo summarizing trade-offs and next actions.
+
+## Agent/Skill Invocations
+- `experimentation-strategist` – orchestrates prioritization + governance alignment.
+- `insight-analyst` – validates data quality and metric assumptions.
+- `hypothesis-library` skill – links past learnings to current ideas.
+- `guardrail-scorecard` skill – enforces readiness requirements.
+
+---

commands/synthesize-learnings.md

@@ -0,0 +1,34 @@
+---
+name: synthesize-learnings
+description: Creates experiment readouts, codifies learnings, and routes follow-up actions.
+usage: /growth-experiments:synthesize-learnings --source exp-log.db --scope "Q4 funnel" --audience exec
+---
+
+# Command: synthesize-learnings
+
+## Inputs
+- **source** – experiment tracker, warehouse table, or analytics workspace.
+- **scope** – filters (timeframe, product area, funnel stage, persona).
+- **audience** – exec | pod | growth-guild | async memo; controls fidelity/tone.
+- **format** – deck | memo | dashboard | loom.
+- **follow-ups** – optional CSV/JSON for linking Jira/Asana action items.
+
+## Workflow
+1. **Data Consolidation** – assemble final metrics, guardrail outcomes, and qualitative notes.
+2. **Insight Extraction** – group learnings by hypothesis theme, persona, or funnel stage.
+3. **Decision Encoding** – record win/ship, iterative, or archive outcomes plus rationale.
+4. **Action Routing** – create follow-up stories, backlog items, or automation triggers.
+5. **Knowledge Base Update** – tag learnings in centralized library with attribution + status.
+
+## Outputs
+- Executive-ready readout with insights, decisions, and KPIs.
+- Learning cards mapped to hypothesis taxonomy + next bets.
+- Action log synced to backlog/project tools.
+
+## Agent/Skill Invocations
+- `insight-analyst` – leads analysis and storytelling.
+- `experimentation-strategist` – ensures learnings feed roadmap + governance.
+- `hypothesis-library` skill – indexes learnings against taxonomy.
+- `experiment-design-kit` skill – suggests iteration ideas based on patterns.
+
+---