speckit-token-analyzer-report

To generate a markdown report from token analysis runs, you need to provide captured run metadata, summary totals, and step-level JSON inputs. The tool aggregates this data to produce a readable markdown or JSON deliverable summarizing your token usage.

The best way to compare token usage across multiple Spec Kit workflow runs is to aggregate the captured run data. The tool calculates totals, averages, and standard deviations to provide a cross-run comparison view for your scenarios.

Yes, you can identify token optimization opportunities from per-step metrics. The analysis highlights the biggest token consumers in your workflow and suggests where to reduce overhead or improve efficiency based on the captured run data.

Producing a token analysis report requires run metadata, summary totals, step-level JSON inputs, and report templating. These elements are necessary to aggregate the data and generate the final markdown or JSON deliverable.

You need a cross-run comparison report when you have completed several Spec Kit workflow runs and want to understand where tokens are spent. It helps you review performance, share insights, and plan your next optimization pass.

Yes, the token analysis report works with raw run files by combining one or more captured runs into a single analysis view. This prevents you from manually stitching together run files to understand your workflow metrics.