product-tracking-instrument-new-feature
Update the tracking plan when a feature ships, changes, or is removed. Assesses whether new events are needed, extends existing events with properties where possible, and produces a versioned mini-delta with changelog entry. Updates .telemetry/tracking-plan.yaml, delta.md, and changelog.md. Use when the user ships a new feature, modifies existing functionality, wants to keep tracking coherent as the product evolves, 'feature shipped,' 'new feature tracking,' 'update tracking for [feature],' 'what tracking does this feature need,' or 'instrument new feature.'
Install
With your agent
Install OMGSkills skill "accoil/product-tracking-skills:skills/product-tracking-instrument-new-feature" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Accoil/product-tracking-skills /tmp/product-tracking-skills && ln -s /tmp/product-tracking-skills/skills/product-tracking-instrument-new-feature ~/.claude/skills/product-tracking-instrument-new-featureFrom README
Feature Instrumentation You are a product telemetry engineer keeping tracking coherent as the product evolves. When a feature ships, changes, or is removed, you determine the tracking impact and apply it. Reference Index | File | What it covers | When to read | |------|---------------|--------------| | references/naming-conventions.md | Event/property naming standards | Naming new events | | references/persistence.md | .telemetry/ folder structure, changelog | Updating artifacts correctly | | references/event-categories.md | Event taxonomy and coverage | Categorizing new events | | references/anti-patterns.md | What to avoid in tracking | Reviewing new additions | Goal When a feature ships or changes, determine: Does this need new tracking? Does it modify existing tracking? Does it need no tracking changes? Then produce a mini delta and update the target plan.
More from this repo
product-tracking-audit-current-tracking
Reverse-engineer the current state of analytics tracking from a codebase.
product-tracking-business-case
Used to write a business case for adding product telemetry and analytics to a product.
product-tracking-design-tracking-plan
Used to design an opinionated target tracking plan and produce an explicit delta from current state to target.