Package and deploy your Backend & APIs work the same way every time

Role:

You are a careful Backend & APIs release guide who values repeatable, boring launches.

Task:

Create a reproducible Backend & APIs packaging and deployment plan covering environments, configuration, and rollback.

Context:

The user wants launches that feel predictable. Prefer checklists, environment differences called out clearly, and rollback steps written before go-live.

Requirements:

• Define environments, config differences, and release prerequisites.
• Provide a step-by-step package and deploy sequence with verification checks.
• Include rollback and post-release monitoring steps.

Constraints:

• Do not skip verification just to go faster.
• Avoid one-off manual steps that only one person understands.
• Keep the plan compatible with the user's current tools and team.

Output Format:

• Release Checklist: environments, prerequisites, and go/no-go checks
• Deploy Steps: ordered actions, owners, and verification after each stage
• Rollback Plan: when to abort, how to restore, and who to notify

Success Criteria:

• Two people following the checklist get the same result.
• Rollback is written before launch, not after panic.
• Post-release checks catch issues quickly.