bluekiwi 0.2.4 → 0.2.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: bk-approve
|
|
3
|
-
description: BlueKiwi approval skill. Handles
|
|
3
|
+
description: BlueKiwi approval skill. Handles pending approvals when resuming a session that was interrupted mid-HITL, or when the user explicitly wants to approve a paused step. During normal execution, HITL approval is handled inline by bk-start/bk-next. Use this skill when the user says "/bk-approve", "approve this", "approve step", or returns to a session where a HITL step is already waiting.
|
|
4
4
|
user_invocable: true
|
|
5
5
|
---
|
|
6
6
|
|
|
@@ -85,15 +85,24 @@ Repeat the loop until reaching an auto_advance=false step.
|
|
|
85
85
|
When execute_step returns `next_action: "wait_for_human_approval"`:
|
|
86
86
|
|
|
87
87
|
1. Call `request_approval` with a brief message summarizing what was done.
|
|
88
|
-
2. Show
|
|
88
|
+
2. Show a summary of what was completed:
|
|
89
89
|
```
|
|
90
|
-
|
|
91
|
-
|
|
90
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
91
|
+
⏸ Awaiting Approval: {step title}
|
|
92
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
93
|
+
{brief summary of the step's output}
|
|
94
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
92
95
|
```
|
|
93
|
-
3.
|
|
96
|
+
3. Immediately ask via AskUserQuestion — do NOT tell the user to type `/bk-approve`:
|
|
97
|
+
- header: "Approve?"
|
|
98
|
+
- options: ["Approve — proceed to next step (Recommended)", "Approve with edits", "Reject — redo this step", "Rewind to earlier step"]
|
|
94
99
|
|
|
95
|
-
|
|
96
|
-
|
|
100
|
+
4. Handle the response:
|
|
101
|
+
- **Approve**: Call `approve_step(task_id=<id>)`, then call `advance` and continue the execution loop.
|
|
102
|
+
- **Approve with edits**: Ask the user what to change, apply the edits, then approve and continue.
|
|
103
|
+
- **Reject**: Ask the user for the reason, call `rewind` to return to this step, tell the user "Rewound. Type `/bk-next` to retry."
|
|
104
|
+
- **Rewind to earlier step**: Switch to `/bk-rewind` flow.
|
|
105
|
+
</HARD-RULE>
|
|
97
106
|
|
|
98
107
|
## Step-Type Handling
|
|
99
108
|
|
|
@@ -132,7 +141,7 @@ Show progress at the start of each step as a single line:
|
|
|
132
141
|
## When Pausing (auto_advance=false only)
|
|
133
142
|
|
|
134
143
|
- **HITL approval required** (execute_step returned `next_action: "wait_for_human_approval"`):
|
|
135
|
-
Call `request_approval`, show
|
|
144
|
+
Call `request_approval`, then immediately show AskUserQuestion for approval (see HITL Pause section). Do NOT stop and wait for `/bk-approve`.
|
|
136
145
|
- **Gate step**: Wait for user response via AskUserQuestion.
|
|
137
146
|
- **Other action step pausing without HITL**: "Type `/bk-next` to proceed."
|
|
138
147
|
|
|
@@ -140,6 +140,6 @@ Repeat the loop until reaching an auto_advance=false step.
|
|
|
140
140
|
### 4. When Pausing
|
|
141
141
|
|
|
142
142
|
- **HITL** (execute_step returned `next_action: "wait_for_human_approval"`):
|
|
143
|
-
Call `request_approval`, show
|
|
143
|
+
Call `request_approval`, then immediately show the HITL approval AskUserQuestion (same as bk-next HITL Pause). Do NOT stop and tell the user to type `/bk-approve`.
|
|
144
144
|
- After completing an action step (auto_advance=false, no HITL): "Type `/bk-next` to proceed."
|
|
145
145
|
- After showing a gate question: Wait for user response. Do not show `/bk-next` hint.
|