review-telemetry

Audit telemetry plans for completeness, consistency, and actionable metrics.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill review-telemetry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-telemetry
Source: https://github.com/tomzx/agents/tree/main/skills/review-telemetry
Command: npx skills add https://github.com/tomzx/agents --skill review-telemetry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Telemetry plans often miss coverage, measurable criteria, or actionable insights. This Skill provides a structured review to ensure plans align with the specification, cross-reference with requirements, and respect context rules.

Core Features & Use Cases

  • Completeness checks: verify every required event and metric is defined.
  • Measurability validation: ensure metrics have clear thresholds and calculation methods.
  • Consistency verification: align event names, entities, and actions with the specification.
  • Use Case: Apply to a telemetry plan for a feature to surface gaps before implementation.

Quick Start

Provide the telemetry plan document (.sdlc/features/FEAT-NNNN-<slug>/telemetry.md) and its specification for review.

Frequently Asked Questions about review-telemetry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a telemetry plan for completeness and actionable metrics?

To audit a telemetry plan for completeness, you provide the telemetry document and its specification. The review verifies required events and metrics are defined, ensures metrics have clear thresholds, and reports coverage gaps for remediation.

What is telemetry plan consistency verification against specifications?

Telemetry plan consistency verification aligns defined event names, entities, and actions with the feature specification. It cross-references the telemetry document with specification.md and requirements.md to ensure schema compliance and identify open questions.

How do I validate that telemetry metrics have clear calculation methods?

Validating telemetry metrics involves measurability checks to ensure every metric has clear thresholds and calculation methods. The review cross-references the telemetry plan with requirements to confirm metrics are actionable and consistent with the schema.

Can I review telemetry plans stored outside the .sdlc/features/ directory structure?

Reviewing telemetry plans outside the .sdlc/features/FEAT-NNNN-<slug>/ directory is not supported. The audit specifically targets telemetry.md files within this path and cross-references the corresponding specification.md and requirements.md files.

Why does my telemetry audit report open questions and gaps?

Telemetry audits report gaps and open questions when the plan misses required event coverage, lacks measurable criteria, or contains naming inconsistencies. These remediation items surface missing actionable insights before feature implementation begins.

Do I need a requirements document to perform a telemetry consistency check?

A requirements document is cross-referenced when present to validate measurability and consistency. The telemetry audit applies to documents under the feature directory and checks alignment with specification.md and requirements.md to surface gaps.