mirror of
https://github.com/bleak-ai/gcontext.git
synced 2026-08-11 13:19:23 +02:00
bernatsamperaandClaude Opus 4.6
87d8575829
The workflow spec requires one folder per step inside runs/example/ (e.g. 1-intake/results.md), not flat files. Fixed browser-recipes, seo-pipeline, and support-ops. release-ops was already correct. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
940 B
940 B
Step 5: Close
Purpose
Post the resolution on the ticket and close it in the tracker.
Input
- The outcome file (step 3): what was resolved.
- The ticket tracker connection: to comment and change status.
Output
The ticket in the tracker is commented and set to "done".
How to execute
- Draft a resolution comment for the ticket. Write it for the person who will read the ticket next (a support agent, the customer, or a teammate). Use plain language: name the affected customer and what changed, do not include internal IDs or technical jargon unless the audience is technical.
- Present the draft comment to the human for approval.
- Post the approved comment on the ticket.
- Set the ticket status to "done" (or the equivalent closed state in the tracker).
- Both the comment and the status change need human approval.
Done when
The ticket has the resolution comment and is in a closed state in the tracker.