/install asking-until-100
Asking Until 100
Overview
Use this skill to slow down execution when the task is underspecified, risky, or expensive to get wrong. Treat "100" as target readiness to proceed, not literal certainty.
Workflow
- Load explicit instructions and repo-local config such as
.asking-until-100.yaml. - Classify the task as
coding,build,architecture,debugging,discovery, orgeneral. - Inspect the repo when it looks relevant so repo-discoverable facts do not turn into avoidable questions.
- Estimate readiness from the configured dimensions in
references/protocol.md. - Choose a questioning mode:
fastfor low ambiguityguidedfor moderate ambiguitydeepfor higher ambiguity or requested rigorreportfor highest-rigor coding and build tasks with decision-critical gaps
- Ask the highest-value questions before taking action.
- Respect the execution gate:
- highest-rigor
codingandbuildtasks default to blocking clarification - other tasks default to explicit assumptions when gaps remain
- highest-rigor
Questioning Style
- Prefer structural, directional, and decision-shaping questions over generic filler.
- Use a working hypothesis when it helps the user react to a proposed path.
- Offer suggested answers when useful, but always leave a free-form path.
- Do not ask for facts that can be inspected directly from the repo.
High-Rigor Report
For highest-rigor coding or build tasks, begin with Provisional Project Structure, then emit:
Working Hypothesis, Architecture Questions, Product Questions, Constraint Questions, and
Decision-Critical Unknowns.
The working-hypothesis section must also summarize the execution gate and blocking dimensions.
See references/coding-report-format.md for the required output order and
scripts/render_project_structure.py for deterministic structure rendering.
References
references/protocol.mdfor readiness, repo-aware escalation, and stop conditionsreferences/config.mdfor config fields, precedence, and asking-intensity behaviorreferences/question-patterns.mdfor question quality rules and option patternsreferences/coding-report-format.mdfor the high-rigor report contractreferences/build-playbook.mdfor build-specific gaps to check before acting
Scripts And Assets
scripts/validate_config.pyvalidates profile filesscripts/preview_question_report.pypreviews questioning output for a promptscripts/render_project_structure.pyrenders prompt-only or repo-aware provisional structuresscripts/explain_profile_merge.pyshows the effective merged profileassets/contains bundled profiles tuned forgpt-5.4withxhighreasoning assumptions
Keep this file concise. Use the references for detailed policy, config, and output examples.
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install asking-until-100 - 安装完成后,直接呼叫该 Skill 的名称或使用
/asking-until-100触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
Asking Until 100 是什么?
Repo-aware questioning protocol for OpenClaw that increases clarification before acting on coding, project-build, architecture, debugging, and implementation... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 222 次。
如何安装 Asking Until 100?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install asking-until-100」即可一键安装,无需额外配置。
Asking Until 100 是免费的吗?
是的,Asking Until 100 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
Asking Until 100 支持哪些平台?
Asking Until 100 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 Asking Until 100?
由 Hongyi3(@hongyi3)开发并维护,当前版本 v0.1.0。