Lean and task-focused: a copy-paste spec template, compact tables, and a 7-step process with no beginner-concept padding; it assumes Claude's OpenTelemetry knowledge and every section earns its place.

Fully executable guidance — concrete file paths (docs/observability/<feature>.md, INDEX.md), exact attribute names, a runnable Python trace-assertion test, and explicit cardinality mitigations.

Clearly sequenced Steps 1–7 with an inline 'Required test assertions' checklist and a spec↔test↔implementation drift feedback loop; change-management and catalog steps make the process self-contained.

No bundle files exist, so the single-file body is appropriately organized into well-labeled sections (When to use, Steps, Anti-patterns, Limitations, References) with external doc URLs as one-level-deep references.

Lists multiple concrete actions — building a per-feature trace spec, defining the trace shape (root span + child spans + key attributes per OpenTelemetry semantic conventions), and driving both implementation reviews and trace-assertion tests.

Explicitly answers both what (build a trace spec defining the trace shape that production code must emit) and when via a direct 'Use before...' clause with three concrete scenarios.

Natural triggers for the audience: 'before instrumenting a new feature', 'spans have grown organically with no agreed shape', and 'after an incident where a debugging session stalled on missing span attributes'.

Clear niche — authoring the declarative trace spec — distinct from the named sister testing skills (opentelemetry-trace-assertions, jaeger-trace-tests), with triggers unlikely to fire for unrelated skills.