원클릭으로 Manus에서 모든 스킬 실행

시작하기

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 저장소 열기 Creator 저장소 보기

다운로드

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.