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.3 KiB
1.3 KiB
Step 2: Execute
Purpose
Execute the approved plan step by step, with human approval for every write operation.
Input
- The plan file from step 1: the steps to execute.
- The product connections: to read and write against the product's systems.
Output
runs/{ticket-id}-{slug}/3-execution-log.md with a numbered list of operations performed. Each operation records:
- Step number: matches the plan.
- Service: which connection was used.
- Operation: read or write, and what was done.
- Details: the specific identifiers, values, or queries involved.
- Result: what happened (success, the value returned, or the error).
How to execute
For each step in the plan:
- Reads: execute immediately. Record the result.
- Writes: present a confirmation block to the human before executing:
- What: the operation in plain words.
- Command: the specific action or API call.
- Impact: what changes and what is affected. Wait for explicit approval. If denied, record "skipped by human" and continue.
- After execution, verify the result. If the result is unexpected, stop and present the situation to the human before continuing.
Record every operation in the execution log, whether it succeeded or was skipped.
Done when
All plan steps are executed (or explicitly skipped) and the execution log is written.