event-tracking plugins

by Matt Corbett

Experimentation & growth-engineering team — agents (experimentation-architect, feature-flag-engineer, product-analytics-instrumentation-engineer) for the APPARATUS that lets a team learn fast and ship safely: feature flags + progressive delivery (kill switches, targeting, flag lifecycle/debt), A/B-test plumbing (assignment, exposure logging, SRM checks, sequential-peeking guards, the results read), and trustworthy event instrumentation (a tracking plan, a consistent event schema, identity stitching, a CDP). The engineering of experimentation — statistical VALIDITY (power/MDE, significance) is applied-statistics'. skills, a decision-tree knowledge bank (flag-vs-config + ship-decision trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Seams: significance -> applied-statistics, hypothesis/outcome -> product-management, rollout -> devops-cicd, pipelines -> data-platform. Requires ravenclaude-core@>=0.7.0.

by Matt Corbett

Martech / event-instrumentation & CDP team — agents (event-taxonomy-architect, instrumentation-engineer) for the ENGINEERING of event collection: the tracking plan / event taxonomy (object-action naming), the identity model (anonymous → known, stitching), CDP & collection-architecture selection (Segment, RudderStack, Snowplow, mParticle; client vs server vs hybrid; warehouse-first / reverse-ETL via Hightouch / Census), and consent & privacy-by-design (Consent Mode, IAB TCF, GPC) plus destination wiring. skills (design-a-tracking-plan, choose-cdp-and-collection-architecture, implement-event-instrumentation-and-consent), a knowledge bank + templates. Distinct from marketing-operations (campaign strategy), analytics-engineering (dbt models events downstream), experimentation-growth-engineering (runs tests on them), data-governance-privacy (org policy/DSAR), and data-platform (warehouse) — the event-collection layer they sit on. Requires ravenclaude-core@>=0.7.0.