Build a release checklist tied to evidence

A release checklist should identify the exact artifact, required checks and the person or process authorizing release. Keep environment changes separate from source edits.

Use a reviewable project copy

Give the product or code teammate the relevant specification and a dedicated project folder or branch. Separate a proposed change from permission to release it. Request a diff or evidence table alongside the recommendation, and run checks that exercise the behavior in question. Generated code and test output still need review in the actual project environment.

Inputs for this workflow: Release procedure, build outputs and required verification steps.

Work through the task

1. Map each requirement to an artifact or check.
2. Identify environment-specific prerequisites.

A brief you can adapt

Create release-checklist.md with artifact version, check, evidence location and approval status. Mark incomplete checks explicitly.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Confirm the artifact being released is the one that passed the recorded checks.

Where this approach can fail

A checklist prepared by an AI teammate does not authorize deployment or prove that a live rollout succeeded.

For the related desktop setup, see local folder.