'clarification' 검색 결과

Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[omh] Vague, underspecified request: one-question-at-a-time clarification. Use when the user says: deep-interview, interview me, clarify, feature shaping, ambiguous product request, one question, 要件を詰めて, 曖昧な要求.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comet Phase 1: Open. Invoke with /comet-open. Explore ideas through OpenSpec, confirm requirements clarification, then create change structure (proposal + design + tasks).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds prioritized manuscript revision plans for major or minor revisions by separating comments that require experiments, analyses, clarification, restructuring, or wording changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turns reviewer comments into structured, professional point-by-point responses linked to manuscript revisions, clarifications, rebuttals, and additional analyses.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

dontbesilent 目标清晰化。用维特根斯坦的语言哲学把模糊的目标审计成可检查的交付物。 触发方式：/dbs-goal、/目标、「帮我搞清楚目标」「我想做个人 IP」「我的目标是成为...」「我想变得更...」 Goal clarification using Wittgenstein's philosophy of language. Audits fuzzy goals into checkable deliverables. Trigger: /dbs-goal, "help me clarify my goal", "I want to become...", "my goal is..."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Act as the user's live meeting sidekick inside the current terminal agent session. Use when the user explicitly asks you, the terminal agent, to watch a meeting, follow the live transcript, answer during the call, offer strategist thoughts, silently watch for risks, or track decisions. Do not use this skill to start or control the separate Minutes Coach HUD; explicit Coach or HUD lifecycle requests belong to minutes-copilot, and an ambiguous request such as "coach me live" requires one short surface clarification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Answer a construction request for information so the site can act on it — a direct answer, the drawing or specification reference that supports it, and an explicit statement of whether it changes cost or programme. Use when asked to respond to an RFI, answer a contractor query, or handle a request for information on site, or when RFIs keep coming back for clarification. Produces the answer with its reference, the cost and time implication stated, the instruction status, the distribution list, and the register entry.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyse a construction bid or tender package for scope gaps, risk-shifting exclusions, unit-rate red flags, and front-loading in the schedule of values. Use when asked to review a bid, level bids, check a tender for gaps, compare sub quotes, or vet a schedule of values before award. Produces a structured bid review with a gap register, exclusion risk table, pricing red flags, and an award recommendation with pre-award clarifications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification strategy for theory-plus-experiments papers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collect and persist structured presentation requirements for Codex Slides, including scenario choice, audience, page count, language, format, research mode, visual direction, source-file roles, and clarification checkpoints. Use when a new deck request is ambiguous or scenario-led.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluate completed mediation-competition problems consisting of general information and confidential packets for both sides. Use when asked to validate, audit, score, quality-control, or assess competition readiness; identify factual, numerical, chronological, authority, commercial-logic, or confidentiality defects; test mediation usefulness, BATNAs, settlement corridors, information asymmetry, and opportunities for firmness, cooperation, imagination, and clarification; or produce an author-only validation report. Perform a qualified partial review when packets are missing. Diagnose by default; do not generate a new problem or edit source packets unless repairs are expressly requested. Requires access to all supplied files and a host capable of reading their formats; otherwise disclose the unreviewed material and resulting limits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Local user-profile maintenance skill for Codex, Claude Code, OpenClaw, OpenCode, and other agent harnesses. Use only when the user explicitly invokes $user-profile-keeper to create, initialize, update, query, correct, delete, export, or audit a local persistent user profile. It can extract durable collaboration preferences, requirement-expression habits, capability boundaries, recurring omissions, risk preferences, privacy boundaries, and typical events from the current session into auditable, confirmable, retractable local profile data. Do not auto-invoke, upload profile data, or replace task-clarifier's normal clarification flow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deep need-clarification skill. Use only when the user explicitly invokes $task-clarifier. Once activated, keep asking until all three goals are met: the user fully understands their own needs, the AI fully understands the user's needs, and the user confirms the AI's understanding is correct. Do not intervene in task execution unless explicitly invoked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a Java change needs independent Behavior-Driven Development guidance from trusted behavior facts through concrete examples and observable scenarios, with focused clarification when behavior is pending or ambiguous. This should trigger for requests such as Apply BDD; Facilitate behavior examples; Discover scenarios with Given When Then; Review these examples for shared domain language; Complete BDD discovery as a self-contained interaction. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Screens biomedical / life-science papers for signs of data fabrication, image manipulation, and statistical anomalies, using the detection techniques distilled from the field's canonical exposure platforms (PubPeer, Data Colada, Science Integrity Digest, For Better Science) and tools (ImageTwin/Proofig, statcheck, GRIM/GRIMMER, Problematic Paper Screener, Seek & Blastn). Use when asked to check a paper/figure for image duplication, blot splicing, impossible statistics, paper-mill or tortured-phrase signals, research integrity, or "is this data faked"; or when a user shares a figure, Western blot, supplementary dataset, or DOI and asks whether it looks manipulated. Reports observable anomalies as questions for clarification — it never accuses anyone of fraud.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill enriches vague prompts with targeted research and clarification before execution. Should be used when a prompt is determined to be vague and requires systematic research, question generation, and execution guidance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Iteratively enhance user requirements into clear, complete, actionable specifications through analysis and clarification. Use when: (1) Users provide initial requirements that need refinement, (2) Requirements are vague, incomplete, or ambiguous, (3) Creating formal specifications from informal descriptions, (4) Identifying missing constraints, edge cases, or acceptance criteria, (5) Clarifying assumptions and implicit dependencies, or (6) Preparing requirements for design, implementation, or verification. Operates interactively: analyze → ask clarifying questions → refine based on responses.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide a user from an unclear idea to an actionable plan through the agent harness's native ask tool and clickable choices. Use when the user wants a guided requirements interview, step-by-step questions, help deciding what to build, or a button-led path from goals to scope, solution, and technology choices. Do not turn an ordinary implementation request or a single clarification into an interview.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Protocol for handling ambiguous decisions and missing/conflicting knowledge during code generation, design, and review. Ensures AI surfaces genuine judgment calls with structured options and stops on hallucination risk instead of silently assuming. Use when a decision has multiple valid approaches, when facts are missing or contradictory, when the user asks 'what should we do here?', 'is this a judgment call?', 'should I ask about this?', 'am I guessing here?', 'what are the tradeoffs?', or when deciding between two reasonable architectural or design options. Also composed by molecules to define how judgment calls and clarification requests are surfaced and resolved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.