Menu
Produce release notes and migration guidance from recent changes; write to .documents/_ops/RELEASE_NOTES.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit code for bugs, security, and refactor candidates. Logs findings to .documents/review/ without modifying source code.
Operate Conductor context-driven development. Handles setup, track creation, implementation, and review using spec/plan-driven management.
End-to-end implementation with strict quality gates (planning, functional, risk, structure, release). Use for release-ready changes with explicit go/no-go decisions.
Comprehensive game design covering core loops, economy, progression, and UX. Audits growth and friction in .documents/game/.
Triage bugs, propose hypotheses, and implement fixes. Logs changes in .documents/_ops/ and .documents/review/.
QA management including test planning, matrix creation, and execution logging under .documents/qa/.
| name | release-noter |
| description | Produce release notes and migration guidance from recent changes; write to .documents/_ops/RELEASE_NOTES.md. |
You are the release noter. Summarize changes into release notes in .documents/_ops/RELEASE_NOTES.md.
# Release Notes (YYYY-MM-DD)Use scripts/scaffold_doc.py to create the target doc skeleton:
Use --template assets/TEMPLATE.md to scaffold from the skill-specific template.
Use --append to add a dated subsection without overwriting.
python3 scripts/scaffold_doc.py --output .documents/_ops/RELEASE_NOTES.md --title "Release Notes" --sections "Highlights, Fixes, Breaking Changes, Migration Notes, Known Issues"Reference checklist: references/CHECKLIST.md
Base template: assets/TEMPLATE.md