@analyticscli/growth-engineer 0.1.0-preview.0 → 0.1.0-preview.2

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@analyticscli/growth-engineer",
-  "version": "0.1.0-preview.0",
+  "version": "0.1.0-preview.2",
   "description": "Growth Engineer CLI for connector setup, scheduling, health checks, and OpenClaw-compatible growth runs.",
   "license": "MIT",
   "type": "module",
   "repository": {
     "type": "git",
-    "url": "https://github.com/Wotaso/growth-engineer-cli.git"
+    "url": "git+https://github.com/Wotaso/growth-engineer-cli.git"
   },
   "homepage": "https://github.com/Wotaso/growth-engineer-cli#readme",
   "bugs": {

package/templates/config.example.json

@@ -55,39 +55,39 @@
   },
   "schedule": {
     "intervalMinutes": 1440,
-    "connectorHealthCheckIntervalMinutes": 720,
+    "connectorHealthCheckIntervalMinutes": 360,
     "skipIfNoDataChange": true,
     "skipIfIssueSetUnchanged": true,
     "cadences": [
       {
         "key": "daily",
-        "title": "Daily production guardrail",
+        "title": "Daily Sentry and production guardrail",
         "intervalDays": 1,
         "criticalOnly": true,
-        "focusAreas": ["crash", "conversion", "paywall"],
-        "sourcePriorities": ["sentry", "glitchtip", "analytics", "asc_cli", "revenuecat"],
-        "objective": "Only investigate critical production blockers and business anomalies: Sentry/GlitchTip production errors, crashes, very low users, conversion, purchases, or other urgent drops.",
-        "instructions": "Do exact root-cause analysis with connected production data, memory/state, release context, and recent code changes. Produce the fix or next debugging step; avoid generic growth ideas."
+        "focusAreas": ["sentry_errors", "crash", "onboarding", "conversion", "paywall", "purchase"],
+        "sourcePriorities": ["sentry", "glitchtip", "analytics", "revenuecat", "asc_cli", "feedback", "github"],
+        "objective": "Analyze every configured project for critical production blockers: Sentry/GlitchTip errors, crashes, onboarding or purchase drop-offs, zero-conversion days, missing buyers, very low users, and other silent business anomalies.",
+        "instructions": "Compare against recent baselines across connected sources and code changes. If the finding is critical, produce the exact fix or next debugging step and prefer a GitHub issue or draft PR when GitHub write access is configured; otherwise hand off via OpenClaw chat. Avoid generic growth ideas."
       },
       {
         "key": "weekly",
-        "title": "Weekly conversion, traffic, and RevenueCat review",
+        "title": "Weekly executive product and growth summary",
         "intervalDays": 7,
         "criticalOnly": false,
-        "focusAreas": ["conversion", "paywall", "onboarding", "marketing", "retention"],
-        "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback", "sentry"],
-        "objective": "Analyze total conversion, traffic quality, activation, retention, RevenueCat trials/subscriptions/revenue/churn, source mix, reviews, releases, and stability.",
-        "instructions": "Pick one to three high-confidence growth bets with evidence, expected KPI movement, likely code/store surfaces, and verification plan."
+        "focusAreas": ["conversion", "paywall", "onboarding", "marketing", "retention", "stability"],
+        "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback", "sentry", "github"],
+        "objective": "Create an executive summary across all configured projects, connectors, recent releases, code changes, revenue, activation, retention, reviews, and production stability.",
+        "instructions": "Pick one to three high-confidence improvements with evidence, expected KPI movement, likely code/store surfaces, owner-ready next steps, and a verification plan. Create GitHub issues or draft PR proposals only when the evidence is specific enough."
       },
       {
         "key": "monthly",
-        "title": "Monthly business and product review",
+        "title": "Monthly deep product, business, and code review",
         "intervalDays": 30,
         "criticalOnly": false,
-        "focusAreas": ["conversion", "paywall", "retention", "marketing", "onboarding"],
-        "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback", "sentry"],
-        "objective": "Compare MRR, trial conversion, churn, acquisition quality, store conversion, retention, review themes, feature usage, and crash totals month-over-month.",
-        "instructions": "Decide what should be built, changed, or deleted next and explain why it should move revenue, activation, retention, or acquisition quality."
+        "focusAreas": ["conversion", "paywall", "retention", "marketing", "onboarding", "codebase"],
+        "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback", "sentry", "github"],
+        "objective": "Compare all configured projects month-over-month: MRR, trial conversion, churn, acquisition quality, store conversion, retention, review themes, feature usage, crash totals, and codebase changes.",
+        "instructions": "Decide what should be built, changed, deleted, or instrumented next. Tie conclusions to connector data plus codebase evidence and explain why each recommendation should move revenue, activation, retention, stability, or acquisition quality."
       },
       {
         "key": "quarterly",
@@ -95,8 +95,8 @@
         "intervalDays": 91,
         "criticalOnly": false,
         "focusAreas": ["marketing", "paywall", "retention", "conversion", "onboarding"],
-        "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback"],
-        "objective": "Revisit positioning, pricing/packaging, onboarding architecture, roadmap assumptions, tracking quality, and major funnel bets.",
+        "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback", "github", "sentry"],
+        "objective": "Revisit positioning, pricing/packaging, onboarding architecture, roadmap assumptions, tracking quality, codebase constraints, and major funnel bets across every configured project.",
         "instructions": "Find structural constraints and durable opportunities. Tie recommendations to cohort behavior, monetization, reviews, channel quality, and shipped changes."
       },
       {
@@ -106,7 +106,7 @@
         "criticalOnly": false,
         "focusAreas": ["retention", "conversion", "paywall", "marketing", "general"],
         "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback", "sentry"],
-        "objective": "Audit connector coverage, SDK instrumentation, event taxonomy, data reliability, memory, growth loops, and whether strategy still matches the best users.",
+        "objective": "Audit connector coverage, SDK instrumentation, event taxonomy, data reliability, memory, growth loops, and whether product/code strategy still matches the best users across configured projects.",
         "instructions": "Prioritize measurement fixes and system changes that make future analysis more trustworthy. Identify stale events, missing attribution, weak identity, and misleading dashboards."
       },
       {
@@ -116,7 +116,7 @@
         "criticalOnly": false,
         "focusAreas": ["marketing", "retention", "paywall", "conversion", "general"],
         "sourcePriorities": ["analytics", "revenuecat", "asc_cli", "feedback", "sentry"],
-        "objective": "Reset strategy from evidence: market/channel fit, monetization model, retention ceiling, product scope, and whether to double down, reposition, rebuild, or sunset major surfaces/features.",
+        "objective": "Reset strategy from evidence across every configured project: market/channel fit, monetization model, retention ceiling, product scope, and whether to double down, reposition, rebuild, or sunset major surfaces/features.",
         "instructions": "Use the full year of memory, releases, revenue, acquisition, reviews, code changes, and cohort behavior. Produce strategic experiments and stop-doing decisions."
       }
     ]