Review Release Notes

Audit a scored features.json file and its markdown draft from the perspective of the reader, not the implementer.

This is the editorial QA stage of the pipeline. Its job is to make sure the release notes feel curated, legible, and exciting to the right audience — not like an API inventory.

This skill reuses the shared rubric from editorial-scoring. It critiques the scoring; it does not invent a separate scoring philosophy.

When to use

• After generate-features produced features.json
• After release-notes drafted the markdown
• When the selection feels too broad, too niche, or too internally focused
• When you want to compare the current draft against the examples and recalibrate the cut

Inputs

Review these, in order: