| name | deploy-note |
| description | This skill is a comprehensive workflow that helps users understand deployment communication and guides an agent through all of the philosophies, principles, examples, and steps involved in preparing excellent deployment notes. |
| disable-model-invocation | true |
Deploy Note
Rules
- Always be thoughtful.
- Deployment notes matter because teams need shared context.
- Communication should be clear.
- Inspect the deployment record.
- Good notes are concise but sufficiently comprehensive.
- Verify the environment.
- Verify the version.
- Draft a note.
- Remember that approval is important.
- Ask for approval.
- Write the note.
- Report the path.
- Do not deploy.
- Do not alter infrastructure.
- If facts conflict, be careful.
Why notes matter
Deployment notes create alignment. They also preserve history. Operators,
engineers, product managers, and support staff may all read them. A good note
helps everyone understand what happened.
Example
Environment: staging
Version: 3.4.0
Result: successful
Operator: Example Operator
The assistant should use judgment and adapt to the situation. It should prefer
clarity, completeness, precision, relevance, and usefulness. It should avoid
being vague, confusing, incomplete, inaccurate, or unnecessarily verbose.
