Back to the Playbook
OperateOP-01
Prepare release
Verify that a release is ready across scope, quality, measurement and communication before deployment.
Product statusAssisted workflow
Context in4 required inputsRelease scope and completed stories · Test and review status · Success metrics
TransformationProduct Manager + QA Agent + Product AgentAtlassian · Code Analysis · Local Files
OutcomeRelease readiness decision with remaining actions.Artifact: Release plan
Owner
Product Manager
Human-led
Participants · Agents
EngineerQA AgentProduct Agent
Trigger
A planned release approaches deployment.
Required context
JiraRelease scope and completed storiesCodeTest and review statusProduct BrainSuccess metricsJiraKnown issues
Optional context
FilesRollout planFilesSupport readinessFilesCustomer communication needs
Skills
AtlassianCode AnalysisLocal Files
Methods used inside this Activity: Release readiness checklist
Activity steps
- 1Verify the scope against the plan and check for blockers.
- 2Confirm review status and measurement readiness.
- 3Review rollout and rollback.
- 4Decide readiness and list the remaining actions.
Output
Release readiness decision with remaining actions.
Artifacts
Creates: Release plan
What good looks like
- No hidden blockers.
- Measurement is ready before shipping.
- Rollback and known risks are explicit.
- Communication needs are identified.
Quality gate
Release owner and engineering approve the release.
Destination
JiraTeklens only
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.