Codex
Claude
GeminiWhat you do
- Review the completed support conclusion in the canonical Slack thread.
- Give the required same-thread instruction to create delivery work.
- Inspect the created task link and engineering handoff.
Support and engineering teams converting verified issues into delivery work / support
Delivery Task Handoff
A delivery-ready tracker task linked back to the approved support thread and handed to engineering without changing the product.
From request to resultA complete plan you can follow.
Visible planThe problem
Support conclusions lose evidence or create premature engineering tasks when investigation, operator authorization, and delivery acceptance are mixed together.
AI can translate an evidence-backed conclusion into complete delivery context while the operator retains task-creation authority.
What the agent does
- Verify the investigation is complete and the same-thread authorization is current.
- Create the task with reproduction, impact, evidence, acceptance criteria, and dependencies.
- Reply with the task ref, add the task-created signal, and hand off to engineering.
When this workflow helps
A reusable method, adapted to the request.
- A support.issue-investigation conclusion is posted and the operator replies in the same canonical thread asking for delivery work.
- The task must preserve source, thread, media, conclusion, instruction, and handoff refs.
- Engineering delivery should start from tracker state rather than chat-only context.
Before it starts
Connection required
- A completed support conclusion in the canonical Slack thread
- A current same-thread instruction authorizing task creation
- Project workflow and tracker context
What proves it worked
Evidence, not a success claim.
- Linked investigation evidence
- Delivery-ready tracker task
- Slack acknowledgement and task-created signal
- Engineering workflow handoff
Workflow path
The reusable stages of the work.
A real run expands these stages around the request, context, selected tools, approvals, and dependencies.
- 01Passes to next stage
Confirm Thread Instruction
Re-read the canonical thread and confirm the task instruction belongs to the same thread as the support conclusion.
- 02Passes to next stage
Create Delivery Task
Create delivery-ready tracker work with cause, scope, acceptance criteria, verification expectations, and preserved chat refs.
- 03Passes to next stage
Post Task Handoff
Reply in the canonical thread with the task link/key, scoped delivery summary, and engineering.tracked-delivery handoff.
- 04Verified outcome
Add Task-Created Reaction
Add a semantically matching reaction to the canonical message only after task creation succeeds.
Safe stopping and recovery
Useful even when the whole path cannot run.
- Stop with a same-thread clarification when task creation was not explicitly authorized.
- If authorization or required delivery context is missing, ask in the same thread and create nothing.
- If acknowledgement fails after task creation, reuse the existing task ref rather than duplicating work.
Documented follow-on work
The next workflow is conditional, not hidden.
Specialists inside this workflow
Clear roles for each part of the job.
Connected work