feat(grilling): omp-aware interview redesign, absorb ask-etiquette law #20
@@ -16,7 +16,7 @@ Work the tree in **rounds**: ask the whole frontier at once, then wait. A decisi
|
||||
Ask each closed decision - anything expressible as 2–5 options - through the `ask` tool:
|
||||
|
dank marked this conversation as resolved
Outdated
|
||||
|
||||
- **One artefact per question**, counted before sending. Name the artefact each question decides; two names means two questions. Shared plumbing (an endpoint, a service, a build step) still leaves two artefacts.
|
||||
- Recommended answer first, marked `recommended: 0`: the user's single Enter accepts it.
|
||||
- Recommended answer first, marked `recommended: 0`, which labels it "(Recommended)" for one-glance acceptance. Every reply names what was picked, so the record is unambiguous.
|
||||
- Options quote the user's goal. Their words, their stated goal, ground the wording; your todo text and table rows stay out of it.
|
||||
- Your own idea is welcome: it gets its own recommended question. Attach it to its own question, so it rides there on its merits.
|
||||
- `multi: true` for pick-many, `header` for the branch chip, `preview` when the decision needs code or config in front of the user.
|
||||
|
||||
Reference in new issue
Block a user
Drop this line; this skill is not a history.