refactor(skills): inline grill turn endings
This commit is contained in:
@@ -73,8 +73,9 @@ A completed grill summary is not an instruction to build.
|
||||
Probe vague words, overloaded terms, and hidden assumptions.
|
||||
Use concrete scenarios to test concept boundaries and edge cases.
|
||||
When code contradicts the user's claim, quote both the claim and the code behavior.
|
||||
If the turn includes a correction, file edit, apology, or explanation, still end with the next numbered question.
|
||||
|
||||
Finish when the turn ends with one numbered question, summary, or pause statement.
|
||||
Finish when the turn ends with the next numbered question.
|
||||
|
||||
5. Close or pause.
|
||||
Close when `Open questions:` and `Blocked questions:` are empty.
|
||||
@@ -82,15 +83,6 @@ A completed grill summary is not an instruction to build.
|
||||
Include optional follow-up questions that were not added to either section.
|
||||
Do not act on the summary unless the user gives a new implementation instruction.
|
||||
If the user changes tasks, state that grill is paused.
|
||||
End the turn with the final decision summary or the pause statement.
|
||||
|
||||
Finish when the summary is delivered or grill is explicitly paused.
|
||||
|
||||
## Turn endings
|
||||
|
||||
While grill is active, every assistant turn must end with exactly one of these items:
|
||||
|
||||
- the next numbered question
|
||||
- the final decision summary
|
||||
- a plain statement that grill is paused because the user changed tasks
|
||||
|
||||
If the turn includes a correction, file edit, apology, or explanation, still end with the next numbered question.
|
||||
|
||||
Reference in New Issue
Block a user