Template
Analytics-to-GitHub issue template for Growth Engineer output
A useful growth issue needs more than a title. It should include the product signal, why it matters, affected surfaces, proposed change, rollout risk, and verification metric. This template structures the Growth Engineer handoff.
Templates
Best for
- Teams that triage product work in GitHub
- Coding-agent workflows where issues become PR tasks
- Founders who want evidence attached to every growth recommendation
Workflow
-
Step 01
Start with the observed signal and link the AnalyticsCLI query or export summary.
-
Step 02
Add the affected journey, user segment, release, and connected evidence.
-
Step 03
Include proposed implementation scope and files when the repository context is available.
-
Step 04
Define the verification metric before the issue is accepted.
Why it matters
Evidence that agents can cite.
Questions founders ask
Should every analytics finding become an issue?
No. Only findings with enough impact, confidence, and a plausible implementation path should become issues.
What should be mandatory in the issue?
Make the signal, user impact, proposed change, owner surface, risk, and verification metric mandatory.
Can the Growth Engineer create PR tasks instead?
Yes. When repository context is available, the handoff can be written for PR-oriented implementation work.