Skills › BMAD Method › bmad-toolsmith › sample-capability.md
sample-capability.md
14 lines · skills/bmad-toolsmith/shapes/agent/assets/sample-capability.md at bd70c64
1# Release notes
3The outcome is the entry for the version being released in `CHANGELOG.md`. A user upgrading reads it without the commit log in front of them, so every line names what changed for them, never the commit, and anything that needs a step from them sits under its own `Upgrade` heading at the top.
Release notes
The outcome is the entry for the version being released in CHANGELOG.md. A user upgrading reads it without the commit log in front of them, so every line names what changed for them, never the commit, and anything that needs a step from them sits under its own Upgrade heading at the top.
5## What you cannot infer
7- The range is the last `v*` tag to `HEAD` unless the user names one.
8- Groups are Added, Changed, Fixed, Removed, in that order; an empty group is left out. Dependency bumps are one line together.
9- Commits typed `chore`, `ci` and `test` are left out unless they change what a user sees.
10- A commit whose effect you cannot tell from its message is one question to the user, listing the commits, not a guess: a wrong line here reaches every user of the release.
What you cannot infer
- The range is the last
v*tag toHEADunless the user names one. - Groups are Added, Changed, Fixed, Removed, in that order; an empty group is left out. Dependency bumps are one line together.
- Commits typed
chore,ciandtestare left out unless they change what a user sees. - A commit whose effect you cannot tell from its message is one question to the user, listing the commits, not a guess: a wrong line here reaches every user of the release.