What problem does it solve?
After all stories in an iteration are developed and committed, teams still need to manually assemble a version changelog, aggregate development efficiency metrics (code changes, duration, credit and token costs), clean up temporary files, and bump the patch version. This Skill automates that entire closing phase of the iteration pipeline.
Core Features & Use Cases
- Changelog Generation: Scans each story's commit.md in sequence order and appends a versioned section (e.g., v0.9.3) to changelog.md without overwriting history.
- Efficiency Metrics Aggregation: Reads iteration-state.json to produce a three-layer summary.md covering iteration totals, per-story statistics, and per-stage cost breakdowns (credit, input/output/cache tokens, call counts).
- Iteration Housekeeping: Deletes the .tmp/ directory, increments the patch field in iteration-state.json, then commits and pushes results to the iteration branch.
- Use Case: When every story in specs/v0.9.x reaches the committed phase, run this Skill to produce the v0.9.3 changelog and cost report, then push the finalized iteration branch to the remote repository.
Quick Start
Run the iteration report for specs/v0.9.x now that all stories are committed, generating the changelog and summary, then push the iteration branch.
