alexion/dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(skills): split grill change and state markers

Browse Source
This commit is contained in:
alexion
2026-09-08 11:07:13 -04:00
parent ebf7d2f430
commit 63b44c1dca
1 changed files with 19 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
src/skills/grill/SKILL.md
View File

@@ -66,32 +66,39 @@ When code contradicts the user's claim, quote both the claim and the code behavi
## Open-question accounting
Use `- [ ]` for ready unresolved questions, and keep them visible every turn.
Use `- [b]` for blocked questions, and keep them visible every turn.
Use `- [+]` for questions added by the latest answer.
Use `- [u]` for questions updated by the latest answer.
Use `- [x]` for questions resolved by the latest answer.
Use `- [-]` for questions removed by the latest answer.
Use the line prefix to show list changes on the current turn:
Show `- [u]`, `- [x]`, and `- [-]` for one turn only.
- `-` for unchanged, resolved, or removed questions
- `+` for questions added by the latest answer
- `~` for questions updated by the latest answer
Use the bracket state to show the question state:
- `[ ]` for ready unresolved questions
- `[b]` for blocked questions
- `[x]` for resolved questions
- `[-]` for removed questions
Keep `- [ ]` and `- [b]` questions visible every turn.
Show `+`, `~`, `[x]`, and `[-]` for one turn only.
After that turn, keep an updated question visible as `- [ ]` or `- [b]`.
After that turn, remove resolved and removed questions from the visible list.
Use `- [b]` for questions the agent knows exist but cannot ask yet.
When a blocked question becomes askable, mark it with `- [u]` for one turn.
Do not use `- [+]` for unblocked questions because they are not new.
When a blocked question becomes askable, mark it with `~ [ ]` for one turn.
Do not use `+ [ ]` for unblocked questions because they are not new.
Add questions only when the latest answer directly causes them.
When the user extends scope instead of answering, account for the new question before pursuing it.
Do not add optional follow-up questions to the open-question list.
Put optional follow-up questions in the final summary instead.
Include a cause note for each `- [+]`, `- [u]`, and `- [-]` change.
Include a cause note for each `+`, `~`, and `[-]` change.
Use this format:
```md
- [+] Policy action names
Cause: Your answer introduced `ALLOW` and `DENY`, changing the prior action names.
+ [b] Patent explicitness
Cause: Your answer made patent terms relevant to the license choice.
```
Preserve agent judgment when the user reframes or invalidates a question.