wrapup-sprint

Sprint wrap-up automation handles retrospective generation, markdown changelog updates, git release tag creation, and SBOM attachment. This Skill executes these tasks sequentially to finalize development cycles and prepare repositories for subsequent sprints.

SLSA provenance provides verifiable metadata documenting how software artifacts were built. You need it for artifact-based sprint wrap-ups to establish supply chain security and traceability using the slsa-framework and cosign signing.

Generating a sprint retrospective in markdown or YAML involves structuring sprint outcomes into standardized documents. This Skill processes sprint data to produce retrospective files in your chosen markdown or YAML format automatically.

Yes, attaching SBOM and SLSA provenance during release tagging requires syft to generate software bills of materials and cosign for artifact signing and verification. These dependencies enable secure supply chain practices for artifact-based projects.

Yes, the sprint wrap-up tool integrates with existing git repositories by manipulating markdown and YAML files directly. It appends new version sections to your CHANGELOG.md, creates git release tags, and pushes them to your repository.

Automating release tagging and provenance is limited for non-artifact projects because SBOM generation and SLSA attachment are designed for artifact-based workflows. Projects lacking compiled artifacts may not benefit from the syft and cosign provenance features.