​
Completed state

At the end of this guide, the launch-announcement Issue contains its output, Agent Run evidence, a structured reviewer decision with a comment, and a clear next owner. Accepted work is closed; work needing changes or input remains open and routed.

​
Prerequisites

The Issue must be in a reviewable state with a named reviewer. The assignee should attach or link the output, validation notes, known risks, and the relevant Agent Run. Review judges whether the output meets the request. Approval is a separate decision that authorizes a governed action.

​
Review the launch announcement

  1. Open the Issue and restate the acceptance criteria: correct setup command, supported claims, named audience, and a Markdown deliverable.
  2. Open the announcement itself. Do not judge quality from the Run summary alone.
  3. Inspect the Agent Run result, runtime and model, cost when available, transcript, raw evidence, validation, and terminal status. Use raw logs only where the readable evidence leaves a question.
  4. Check that the output is connected to this Issue and Run, and that any source links are references rather than mislabeled produced output.
  5. Record one structured reviewer decision with a specific comment. Accept when the criteria are met; request changes when the assignee should revise; choose blocked when required evidence or access is missing.
  6. If the review identifies separate work, create or link a follow-up instead of hiding it in a vague acceptance comment.

​
Success signal

A later reader can see what was reviewed, which evidence supported the decision, why the reviewer chose it, and who owns the next action. Acceptance completes the Issue only through the structured path. Requested changes return to the assignee with the review comment preserved.

​
Recovery

If the output or evidence is missing, do not accept the work. Request the exact file, source, test, screenshot, or Run detail needed for judgment. If the reviewer Run ends without a structured decision and the Issue remains in_review, Rudder may schedule bounded reviewer follow-up; the free-form response does not become acceptance. If review reveals a reusable lesson, preserve the feedback with its evidence. Do not edit a Skill, Agent instruction, workflow, or decision silently. Propose the target, scope, evaluation, approval path, and rollback before promoting it.