This guide uses an Issue for a launch announcement. Use the same flow for any task that benefits from a clear owner, status, and reviewer.

​
What the finished Issue should show

The final record should make it easy to find the original request, the owner, the Agent Run, the result, the review comment, and any follow-up work.

​
Before you start

Prepare:
  • one result you can describe clearly
  • a short list of acceptance criteria
  • one person or Agent to do the work
  • a reviewer only when independent judgment matters

​
Move the task through its lifecycle

  1. Create the Issue. Use a specific title such as Draft the launch announcement. Describe the audience, required content, output format, and how the result will be judged.
  2. Keep it in backlog while decisions are missing. Do not assign vague work just to make the board look active.
  3. Move it to todo and assign one owner. A ready Issue assigned to an Agent can start automatically, so do not also launch a duplicate Run.
  4. Follow the work. The Issue moves to in progress while the owner works. Open the Agent Run to see progress, errors, or output.
  5. Attach the result. Link the Markdown file, preview, screenshot, test output, or other deliverable from the Issue.
  6. Move it to review. Do this only when another person can judge the actual result.
  7. Record the decision. The reviewer accepts the work, requests specific changes, or explains what is blocking the decision. Acceptance can complete the Issue; requested changes return the next step to the assignee.
An ordinary comment saves context. If you need a specific Agent to act on a comment, mention it directly. The mention wakes that Agent but does not change the Issue’s assignee.

​
Check the result

Open the completed Issue as if you had not seen the task before. You should be able to answer:
  • What was requested?
  • Who did the work?
  • Where is the result?
  • How was it checked?
  • Why was it accepted?
  • Is there any follow-up?

​
When the task does not finish cleanly

  • The Run fails: keep the Issue open, link the failed Run, and retry only after understanding the error.
  • Another person or dependency must act: move the Issue to blocked and name what will unblock it.
  • The result is incomplete: request changes instead of accepting it.
  • The review never happens: keep the Issue in review and return it to the named reviewer.
  • A completed task needs more work: reopen it with a comment that explains why, or create a separate follow-up Issue.
For a compact status table, see Issue statuses.