一键在 Manus 中运行任何 Skill

开始使用

handling-ambiguity

星标5

分支0

更新时间2026年6月1日 21:28

When a request is unclear or underspecified, resolve it well instead of guessing

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

New1Direction

New1Direction/korgex

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件开发工程师计算机与数学类职业·SOC 15-1252

SKILL.md

readonly

name	handling-ambiguity
description	When a request is unclear or underspecified, resolve it well instead of guessing
version	1
trust	built-in

Most failed tasks come from confidently building the wrong thing. Calibrate between asking and assuming — both extremes waste the user's time.

Separate the unknowns. What can you resolve yourself from the code, the conventions, or sensible defaults? What genuinely changes what you'd build?
Resolve what you can. For anything with an obvious or conventional answer, pick it, state the assumption, and proceed — don't ask about it.
Ask only blocking, high-leverage questions. If an unknown would change the approach and you can't resolve it, ask ONE crisp question (offer concrete options). Use AskUserQuestion for real forks; don't ask permission to do the obvious.
Scope check. If the request is huge or spans multiple subsystems, surface that and propose a decomposition before diving in.
When you proceed on assumptions, make them visible so the user can correct course early rather than after the work is done.

Red flags: asking a question you could answer by reading one file; OR building for 20 minutes on an unstated assumption that turns out wrong.

同仓库更多 Skills

同仓库

react-doctor

New1Direction/korgex

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

2026-06-055

security-scan

New1Direction/korgex

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

2026-06-035

browser-automation

New1Direction/korgex

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

2026-06-025

verifiable-orchestration

New1Direction/korgex

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

2026-06-025

building-an-mcp-server

New1Direction/korgex

Author or connect a Model Context Protocol server so an agent gains new tools

2026-06-015

ci-cd-pipelines

New1Direction/korgex

Build automated pipelines that gate merges and ship reliably

2026-06-015

name	handling-ambiguity
description	When a request is unclear or underspecified, resolve it well instead of guessing
version	1
trust	built-in

Most failed tasks come from confidently building the wrong thing. Calibrate between asking and assuming — both extremes waste the user's time.

Separate the unknowns. What can you resolve yourself from the code, the conventions, or sensible defaults? What genuinely changes what you'd build?
Resolve what you can. For anything with an obvious or conventional answer, pick it, state the assumption, and proceed — don't ask about it.
Ask only blocking, high-leverage questions. If an unknown would change the approach and you can't resolve it, ask ONE crisp question (offer concrete options). Use AskUserQuestion for real forks; don't ask permission to do the obvious.
Scope check. If the request is huge or spans multiple subsystems, surface that and propose a decomposition before diving in.
When you proceed on assumptions, make them visible so the user can correct course early rather than after the work is done.

Red flags: asking a question you could answer by reading one file; OR building for 20 minutes on an unstated assumption that turns out wrong.