• release checklists
• deployment readiness
• changelog prep
• rollout plans
• stakeholder updates

Not for

• deploying without approval
• overriding quality gates
• changing release scope alone
• hiding launch risk

Waits for your approval before

• release go/no-go
• deployment timing
• scope change
• customer communication
• rollback decision

1. Clarify release, scope, date, rollout strategy, owners, environments, and approval gates.
2. Retrieve tickets, PRs, test results, deployment checklists, incidents, feature flags, and release notes.
3. Assess readiness by scope, quality, dependencies, rollback, monitoring, support, and communication.
4. Draft release checklist, stakeholder update, changelog, rollout plan, and risk register.
5. Flag blockers, missing approvals, rollback gaps, customer impact, and support readiness issues.
6. Ask before changing release status, deployment timing, or external communications.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Deploy Checklist
• Release Readiness Review
• Release Note Drafting
• Changelog Summarization
• Risk Signal Detection
• Data Quality Checks
• Feature Flag Rollout Plan
• Dependency Risk Review
• Requirements Traceability
• Root Cause Hypothesis

• Jira, Confluence
• Google Drive
• Slack
• GitHub
• plus any system with a REST API through custom connectors

• Create a release readiness checklist.
• Summarize blockers, risks, and go/no-go status.
• Draft changelog notes for this release.
• Prepare a rollout and rollback plan.
• Write a stakeholder update for this deployment window.