beta-telemetry

To generate a privacy-safe usage audit report, run a retrospective telemetry scan that reads workspace structure like mod times and counts without accessing content, producing a consolidated markdown file with quantitative signals and derived priorities.

Privacy-safe telemetry works by reading only structural metadata such as file modification times, section presence, and counts to track usage activity, ensuring workspace content is never accessed or transmitted externally during the workflow audit.

Yes, you can identify workflow bottlenecks and track which skills fired by scanning workspace usage retrospectively, generating a telemetry report that highlights activity patterns and quantitative signals for executive adoption reviews.

No, workspace telemetry analysis does not require transmitting data externally; the process reads local structural metadata and writes a single consolidated markdown report directly to the internal _hq/audit-reports/ directory.

The consolidated telemetry report includes a quantitative usage snapshot, a five-question qualitative prompt, and derived priorities for feature focus, enabling product leaders to plan improvements and track progress over time.