yigityildiz0 Product Tracking: Feature Update
Keep telemetry current as the product changes without accumulating unreviewed events.
Workflow
- Read the feature brief, acceptance criteria, relevant tracking plan, and current code boundary.
- Identify the user decision or value moment that the feature changes. If there is none, explain why new telemetry may be unnecessary.
- Propose a small delta: added, changed, deprecated, and intentionally unchanged events.
- Update event contracts, identity/consent implications, measures, and test cases.
- Implement only after the delta is reviewed, then verify source, tests, and documentation agree.
Output
Use a short change record:
Feature and decision link
Added / changed / deprecated events
Schema and privacy impact
Implementation locations
Validation evidence
Rollback or removal condition
Guardrails
- Do not duplicate an existing event under a new name merely because the UI changed.
- Preserve historical comparability or document a clean measurement break.
- Do not collect experimental, sensitive, or user-generated content without an explicit legal/privacy decision.