milestone-review

Automating a milestone review involves aggregating sprint reports, code health markers, and feature completion metrics to generate a structured progress document. This skill compiles that data to deliver scope recommendations, velocity analysis, and conditional go/no-go verdicts.

A go/no-go decision is a conditional verdict on whether a milestone is ready to ship based on risk assessments and feature completeness. It is determined by analyzing sprint velocity, technical debt, and producer risk evaluations to decide if the project meets its checkpoint criteria.

Sprint analysis can identify at-risk features and cut candidates by evaluating velocity and technical debt against the milestone scope. This skill scans code health markers and risk registers to highlight features that jeopardize the release, informing scope reduction decisions.

The milestone review process applies to game development and other agile project milestone checkpoints. As long as you can provide sprint reports, code health data, and feature completion metrics, it generates structured reviews with go/no-go verdicts for any software project.

Code health markers like TODO and FIXME comments indicate technical debt and unfinished work, directly feeding into the milestone risk assessment. The skill scans for these markers to evaluate code stability and incorporate the findings into the final go/no-go verdict.

You should avoid automated milestone reviews if your project lacks structured sprint reports, code health metrics, or a defined risk register. The review process relies on aggregating these specific data points to produce accurate scope recommendations and conditional verdicts.