clarify-question-loop
/clarify-question-loop
Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
- Author
- agentlas-ai ↗
- Repository
- Agentlas-OS ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
Original author description
Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions.
How it works
- Procedure
- Budgets and stop rule (briefing interview engine)
- Default Questions
- Plain-Language Question Rule
- Reference
SKILL.md preview
--- name: clarify-question-loop description: "Use when a meta-agent request is too ambiguous to safely generate, package, publish, or adapt without one to five targeted questions." --- # Clarify Question Loop Ask only questions that change the generated package, runtime adapter, safety boundary, or public/private release decision. For `/hep-build` creation or behavior-changing packaging, this is not a substitute for the Builder Interview and Research Gate in `contracts/builder-interview-research-gate.md`. Run that gate first: ask an 8-12 question first batch, research similar agent repositories or comparables and academic/professional theory, then use this clarify loop only for the remaining narrow ambiguities. ## Procedure 1. Classify the current best mode. 2. If single-agent vs team selection would change the package shape and the independent ownership boundaries are unclear, ask before generation. The first batch must include this plain-language question: "이 일을 한 명의 전문가가 처음부터 끝까지 맡으면 되나요, 아니면 조사/분석/검토처럼 여러 전문가가 나눠 맡고 마지막에 합쳐야 하나요?" 3. Follow up on role count, role-specific tools/permissions, whether outputs must be synthesized, and whether artifacts are sequential dependencies or independent parallel packets. 4. Identify missing facts that would change files or safety. 5. Ask one to five short questions, preferably three. If more than five functional-quality questions remain, return to the Builder Interview and Research Gate instead of pretending the package is ready. 6. Do not ask for secrets. Ask for secret names or setup boundaries instead. 7. After answers arrive, re-run mode classification if needed. 8. Generate or repair the package using the answers and list assumptions. ## Budgets and stop rule (briefing interview engine) This loop shares the briefing interview engine's contract (`agentlas_cloud/interview/`): a question is only worth asking if the answer would change execution, not just its phrasing. Respect the surface budget (chat 3-5 in one batch, stormbreaker <= 8 across two batches, build 8-12 plus follow-ups). 'decide later' is always a valid answer — record it as deferred, never re-ask. When answers you auto-confirmed from code/memory reach three in a row, the next question must go to the human. ## Default Questions - Which runtime targets should be supported? - Is this local-only, private-team, public open-source, or marketplace output? - What tools, APIs, files, or services must it use? - What should count as success? - What must it never read, write, publish, or spend? - 이 일을 한 명의 전문가가 처음부터 끝까지 맡으면 되나요, 아니면 조사/분석/검토처럼 여러 전문가가 나눠 맡고 마지막에 합쳐야 하나요? ## Plain-Language Question Rule Never ask non-technical users to choose internal labels such as `single-agent`, `team-builder`, ownership boundary, memory/context, synthesis, or produces/consumes. Translate them before asking: - ownership boundary -> "누가 따로 맡아야 하는 일인지"; - memory/context -> "각자 따로 기억해야 할 자료, 기준, 진행 상황"; - tools/permissions -> "각자 써도 되는 계정, 파일, 웹사이트, 도구"; - synthesis -> "마지막에 결과를 한데 모으는 일"; - sequential dependency -> "앞 사람이 끝낸 결과를 다음 사람이 이어받는 순서". If a question still sounds technical, split it into two shorter everyday questions and give examples such as 조사, 분석, 검토, 승인. ## Reference See `docs/clarify-question-loop.md`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · agentlas-ai/Agentlas-OS | 100 | Apache-2.0 |
| agentlas-ai/Agentlas-OS | 100 | Apache-2.0 |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version ee4dce8ccdae (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90clarify
规范澄清技能. 通过提出最多 5 个高度针对性的澄清问题, 识别当前功能规范中未充分说明的领域, 并将答案编码回规范中. 当用户提到澄清规范、消除模糊性、补充规范细节、或在 specify 完成后需要进一步细化时使用. - 100clarify-underspecified
Ask the minimum clarifying questions before implementing when scope, constraints, or success criteria are unclear. Use when a request has multiple plausible interpretations, missing acceptance criteria, or ambiguous environment constraints. Triggers: "unclear", "ambiguous", "not… - 100clarify
Asks the user sharp clarifying questions about their request before starting, then does the work with their answers. Use only when the user writes /clarify or asks you to clarify first. - 90clarify
Use when the user says "clarify", "what is ambiguous here", or when a prompt or spec reads as under-specified before planning. Not for exploring intent with questions: use askme. - 100align
Surface what I think we're doing before acting on it. Use when the user invokes the align skill, says "let's align first", "check in before you start", or "mirror what you're hearing". Also invoke before starting any task with real interpretive weight. An ambiguous request, a… - 90sdlc-clarify
Resolve the open questions in a draft spec with at most 5 targeted questions and write each answer back into the spec. Use after sdlc-specify when [NEEDS CLARIFICATION] markers or material ambiguities remain, or when the user says 'clarify'.