27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# OpenCode Question Policy
|
|
|
|
Prefer `question` over prose option lists when clarification will materially change the result.
|
|
|
|
## When To Use `question`
|
|
- Use it when there are 2+ meaningful and mutually exclusive options.
|
|
- Use it when the answer changes architecture, config, output format, naming, priorities, workflow direction, or another blocking implementation choice.
|
|
- Ask in the primary agent before delegating to a subagent if the answer must steer delegated work.
|
|
|
|
## When Not To Use `question`
|
|
- Skip it when the user already gave a specific direction.
|
|
- Skip it when only one valid answer exists.
|
|
- Skip it when the choice is cosmetic and does not affect execution.
|
|
|
|
## How To Ask
|
|
- Ask 2-4 options per question.
|
|
- Put the recommended option first.
|
|
- Keep labels short and descriptions to one sentence each.
|
|
- Combine related blocking decisions into one `question` call when possible, with at most 3 questions in the dialog.
|
|
- Do not print a prose preface like `Вот варианты:` before calling the tool.
|
|
- Do not add an `Other` or `Другое` option unless free-form input is not available; the OpenCode UI already supports custom input.
|
|
|
|
## After The Answer
|
|
- Continue the task immediately.
|
|
- Do not repeat the full option list in prose unless the user asks for a recap.
|
|
- If `question` is unavailable, ask one short plain-text question instead.
|