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>
1.1 KiB
1.1 KiB
description, parameters
| description | parameters | |||||||
|---|---|---|---|---|---|---|---|---|
| Resolve a support ticket end to end. Takes a ticket ID or "next" to pull from the queue. |
|
Support Task
Read this workflow's index.md and steps/index.md to load the full procedure.
Resolve the ticket $ticket by executing steps 0 through 5 in order:
- Intake: fetch the ticket, identify the customer and category, set it to in progress.
- Plan: find a matching playbook or propose a custom plan. Stop for approval.
- Execute: run the plan step by step. Reads execute immediately. For every write, present what/command/impact and wait for explicit approval.
- Log: write the structured run folder with intake, plan, execution log, and outcome.
- Learn: create or update a playbook with what was learned.
- Close: post the resolution comment and close the ticket. Both need approval.
Narrate each step as you go. Before any write to an external system, describe what you are about to do and stop for approval.