What problem does it solve? The ptp pipeline runs across many agents and CLIs but emits no durable timing data, making it impossible to attribute work time to epics, commands, or agents. This Skill is the single source of truth for the telemetry contract: the per-epic append-only run ledger, the 26-column spans CSV schema, the loopback OTLP receiver, and the ledger-to-span join rules. ## Core Features & Use Cases - Run ledger contract: Defines the ledger record shape, run_id minting, append protocol, and gate ordering so every write point records runs identically. - Span layer: Specifies the OTLP receiver, the 26-column spans.csv schema, OTel attribute mapping, and tool_class bucketing for Claude Code and Codex spans. - Ledger join and attribution: Joins spans to ledger runs by session and time window, routing unmatched records to _unattributed/ without ever dropping data. - Use Case: Enable telemetry.mode, run ptp pipeline commands, then use the report and analyze subcommands to see aggregate work time, elapsed wall time, and per-tool breakdowns per epic. ## Quick Start Ask the AI to enable ptp telemetry by running the telemetry setup subcommand and then report timing for the current epic.