rudder-instrumentation-planning

Name: rudder-instrumentation-planning
Author: rudderlabs

18stars0forks

How to install rudder-instrumentation-planning?

rudderlabs/rudder-agent-skills/rudder-instrumentation-planning

$npx -y skills add rudderlabs/rudder-agent-skills --skill rudder-instrumentation-planning

Installs into the current project.

Summary

Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy

Files · 1

View on GitHub

SKILL.md

1	# Instrumentation Planning
2
3	This skill guides you through designing an instrumentation strategy - the systematic approach to deciding what events and properties to track in your application.
4
5	## Why Planning Matters
6
7	Poor instrumentation leads to:
8	- Data gaps - Can't answer business questions
9	- Data bloat - Too many events, high costs, noise
10	- Inconsistency - Same action tracked differently across teams
11	- Technical debt - Constant schema changes breaking dashboards
12
13	Good instrumentation provides:
14	- Complete funnel visibility - Every step from acquisition to retention
15	- Consistent naming - Clear conventions everyone follows
16	- Maintainable schema - Easy to extend, hard to break
17	- Actionable insights - Data that drives decisions
18
19	## Choose Your Workflow
20
21	Different starting points require different approaches:
22
23	\| Your Situation \| Recommended Skill \|
24	\|----------------\|-------------------\|
25	\| Building new feature, events not yet defined \| `rudder-design-first-instrumentation` \|
26	\| Existing product needs instrumentation \| `rudder-code-first-instrumentation` \|
27	\| Restructuring existing tracking \| `rudder-code-first-instrumentation` \|
28	\| General planning guidance \| Continue with this skill \|
29
30	### Design-First vs Code-First
31
32	Design-First: Start from product requirements → define events → define properties → implement code. Best for new features where events are part of product definition.
33
34	Code-First: Start from existing code types → derive tracking plan → align with data governance. Best for existing products with domain types already defined.
35
36	This skill covers the general planning process. For workflow-specific guidance, see the specialized skills above.
37
38	## The Planning Process
39
40	```
41	┌─────────────────────────────────────────────────────────────────────┐
42	│ INSTRUMENTATION PLANNING │
43	└─────────────────────────────────────────────────────────────────────┘
44	│
45	▼
46	┌─────────────────┐
47	│ 1. DISCOVERY │ ← What questions do we need to answer?
48	└────────┬────────┘
49	▼
50	┌─────────────────┐
51	│ 2. TAXONOMY │ ← What events and properties will answer them?
52	└────────┬────────┘
53	▼
54	┌─────────────────┐
55	│ 3. BUILD │ ← Create the YAML definitions
56	└────────┬────────┘
57	▼
58	┌─────────────────┐
59	│ 4. ASSEMBLE │ ← Group into tracking plans
60	└────────┬────────┘
61	▼
62	┌─────────────────┐
63	│ 5. INTEGRATE │ ← Generate code, implement in apps
64	└─────────────────┘
65	```
66
67	## Phase 1: Discovery
68
69	### Questions to Ask Stakeholders
70
71	Business Questions:
72	- What KPIs do we track? (conversion rate, retention, revenue)
73	- What funnels do we analyze? (signup, checkout, onboarding)
74	- What experiments will we run? (A/B tests need specific events)
75	- What attribution do we need? (marketing channels, campaigns)
76
77	Product Questions:
78	- What are the key user journeys?
79	- What features do we want to measure adoption for?
80	- What errors/failures do we need to monitor?
81
82	Technical Questions:
83	- What platforms exist? (web, iOS, Android, server)
84	- What existing tracking is in place?
85	- What tools consume this data? (Amplitude, Mixpanel, warehouse)
86
87	### Discovery Template
88
89	```markdown
90	## Business Goals
91	- [ ] Primary KPIs: _______________
92	- [ ] Key funnels: _______________
93	- [ ] Attribution needs: _______________
94
95	## User Journeys to Track
96	1. _______________
97	2. _______________
98	3. _______________
99
100	## Platforms
101	- [ ] Web
102	- [ ] iOS
103	- [ ] Android
104	- [ ] Server
105
106	## Existing Tracking
107	- Current events: ___ events
108	- Issues with current: _______________
109	```
110
111	## Phase 2: Taxonomy Design
112
113	### Step 1: Define Event Categories
114
115	Group events by business domain:
116
117	\| Category \| Purpose \| Examples \|
118	\|----------\|---------\|----------\|
119	\| `user-lifecycle` \| Account actions \| Signed Up, Logged In, Profile Updated \|
120	\| `ecommerce` \| Purchase funnel \| Product Viewed, Added to Cart, Order Completed \|
121	\| `engagement` \| Feature usage \| Feature Used, Content Viewed, Search Performed \|
122	\| `errors` \| Failure tracking \| Error Occurred, Checkout Failed \|
123
124	### Step 2: Map User Journeys to Events
125
126	Example: E-Commerce Funnel
127
128	```
129	User Journey Events
130	─────────── ──────
131	Browse products → Product Viewed
132	Add to cart → Product Added to Cart
133	Start checkout → Checkout Started
134	Complete purchase → Order Completed
135	```
136
137	Example: SaaS Onboarding
138
139	```
140	User Journey Events
141	─────────── ──────
142	Create account → Signed Up
143	Verify email → Email Verified
144	Complete profile → Profile Completed
145	Use first feature → Feature U

People who liked this also viewed

6 picks

Type

rudder-instrumentation-planning

18stars0forks

View on GitHub

How to install rudder-instrumentation-planning?

rudderlabs/rudder-agent-skills/rudder-instrumentation-planning

$npx -y skills add rudderlabs/rudder-agent-skills --skill rudder-instrumentation-planning

Installs into the current project.

Summary

Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy

Files · 1

View on GitHub

SKILL.md

1	# Instrumentation Planning
2
3	This skill guides you through designing an instrumentation strategy - the systematic approach to deciding what events and properties to track in your application.
4
5	## Why Planning Matters
6
7	Poor instrumentation leads to:
8	- Data gaps - Can't answer business questions
9	- Data bloat - Too many events, high costs, noise
10	- Inconsistency - Same action tracked differently across teams
11	- Technical debt - Constant schema changes breaking dashboards
12
13	Good instrumentation provides:
14	- Complete funnel visibility - Every step from acquisition to retention
15	- Consistent naming - Clear conventions everyone follows
16	- Maintainable schema - Easy to extend, hard to break
17	- Actionable insights - Data that drives decisions
18
19	## Choose Your Workflow
20
21	Different starting points require different approaches:
22
23	\| Your Situation \| Recommended Skill \|
24	\|----------------\|-------------------\|
25	\| Building new feature, events not yet defined \| `rudder-design-first-instrumentation` \|
26	\| Existing product needs instrumentation \| `rudder-code-first-instrumentation` \|
27	\| Restructuring existing tracking \| `rudder-code-first-instrumentation` \|
28	\| General planning guidance \| Continue with this skill \|
29
30	### Design-First vs Code-First
31
32	Design-First: Start from product requirements → define events → define properties → implement code. Best for new features where events are part of product definition.
33
34	Code-First: Start from existing code types → derive tracking plan → align with data governance. Best for existing products with domain types already defined.
35
36	This skill covers the general planning process. For workflow-specific guidance, see the specialized skills above.
37
38	## The Planning Process
39
40	```
41	┌─────────────────────────────────────────────────────────────────────┐
42	│ INSTRUMENTATION PLANNING │
43	└─────────────────────────────────────────────────────────────────────┘
44	│
45	▼
46	┌─────────────────┐
47	│ 1. DISCOVERY │ ← What questions do we need to answer?
48	└────────┬────────┘
49	▼
50	┌─────────────────┐
51	│ 2. TAXONOMY │ ← What events and properties will answer them?
52	└────────┬────────┘
53	▼
54	┌─────────────────┐
55	│ 3. BUILD │ ← Create the YAML definitions
56	└────────┬────────┘
57	▼
58	┌─────────────────┐
59	│ 4. ASSEMBLE │ ← Group into tracking plans
60	└────────┬────────┘
61	▼
62	┌─────────────────┐
63	│ 5. INTEGRATE │ ← Generate code, implement in apps
64	└─────────────────┘
65	```
66
67	## Phase 1: Discovery
68
69	### Questions to Ask Stakeholders
70
71	Business Questions:
72	- What KPIs do we track? (conversion rate, retention, revenue)
73	- What funnels do we analyze? (signup, checkout, onboarding)
74	- What experiments will we run? (A/B tests need specific events)
75	- What attribution do we need? (marketing channels, campaigns)
76
77	Product Questions:
78	- What are the key user journeys?
79	- What features do we want to measure adoption for?
80	- What errors/failures do we need to monitor?
81
82	Technical Questions:
83	- What platforms exist? (web, iOS, Android, server)
84	- What existing tracking is in place?
85	- What tools consume this data? (Amplitude, Mixpanel, warehouse)
86
87	### Discovery Template
88
89	```markdown
90	## Business Goals
91	- [ ] Primary KPIs: _______________
92	- [ ] Key funnels: _______________
93	- [ ] Attribution needs: _______________
94
95	## User Journeys to Track
96	1. _______________
97	2. _______________
98	3. _______________
99
100	## Platforms
101	- [ ] Web
102	- [ ] iOS
103	- [ ] Android
104	- [ ] Server
105
106	## Existing Tracking
107	- Current events: ___ events
108	- Issues with current: _______________
109	```
110
111	## Phase 2: Taxonomy Design
112
113	### Step 1: Define Event Categories
114
115	Group events by business domain:
116
117	\| Category \| Purpose \| Examples \|
118	\|----------\|---------\|----------\|
119	\| `user-lifecycle` \| Account actions \| Signed Up, Logged In, Profile Updated \|
120	\| `ecommerce` \| Purchase funnel \| Product Viewed, Added to Cart, Order Completed \|
121	\| `engagement` \| Feature usage \| Feature Used, Content Viewed, Search Performed \|
122	\| `errors` \| Failure tracking \| Error Occurred, Checkout Failed \|
123
124	### Step 2: Map User Journeys to Events
125
126	Example: E-Commerce Funnel
127
128	```
129	User Journey Events
130	─────────── ──────
131	Browse products → Product Viewed
132	Add to cart → Product Added to Cart
133	Start checkout → Checkout Started
134	Complete purchase → Order Completed
135	```
136
137	Example: SaaS Onboarding
138
139	```
140	User Journey Events
141	─────────── ──────
142	Create account → Signed Up
143	Verify email → Email Verified
144	Complete profile → Profile Completed
145	Use first feature → Feature U

People who liked this also viewed

6 picks

Type