Analytics-to-GitHub issue template for Growth Engineer output
Structure every growth issue: signal, impact, surfaces, proposed change, risk, and verification metric.
Growth loop preview
Agent workflow in 60 seconds
OpenClaw and the Growth Engineer: signals in, reviewed issues and PR plans out.
A GitHub issue template for turning AnalyticsCLI evidence and Growth Engineer recommendations into reviewed implementation tasks.
Who this is for
Start here if the problem below sounds familiar. You do not need every connector on day one—just enough signal for the Growth Engineer to propose work you can review.
- Teams triaging growth work in GitHub
- Agents turning issues into PR tasks
- Founders requiring evidence on every recommendation
How it works
The loop is the same across guides: connect evidence, let the agent read it, then ship a reviewed task with a verification metric.
- Start with the signal and link the AnalyticsCLI query or export.
- Add journey, segment, release, and connected evidence.
- Include implementation scope and files when repo context exists.
- Define the verification metric before accepting the issue.
What you get back
The output should be concrete enough to review without opening five dashboards.
- GitHub is a core integration.
- Issue or PR handoffs when configured.
- Evidence and KPIs travel with the task.
Common questions
Quick answers before you connect product data to an agent.
Should every analytics finding become an issue?
No—only findings with impact, confidence, and a plausible implementation path.
What should be mandatory in the issue?
Signal, user impact, proposed change, owner surface, risk, and verification metric.
Can the Growth Engineer create PR tasks instead?
Yes—with repository context for PR-oriented work.