'elicitation' 검색 결과

Manual intent elicitation skill. Use when the user asks to clarify a fuzzy idea, run an elicitation session, design an agent/skill/workflow, identify strategic tension, do a postmortem, align taste/brand direction, or turn vague judgment into an actionable Intent Brief. The skill asks 3–5 sharp questions first, then compiles answers into an Intent Brief and routes the result into system/workflow change. Never run automatically or on a schedule.

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

Facilitate structured requirements gathering. Use when the user says "gather requirements", "elicitation session", "stakeholder interview", "requirements workshop", "what do the users need", "discover requirements", "trawl for requirements", "understand the business need", "conduct interviews", or needs to systematically extract requirements from stakeholders - even if they don't explicitly say "elicitation".

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

Build and troubleshoot C#/.NET MCP servers that expose tools and information to AI agents. Guidance targets the official 2.x SDK and covers transport setup, authentication, interactive features, basic clients, and migration issues caused by changed defaults.

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

• Build a C#/.NET MCP server
• Add tools, prompts, and resources
• Diagnose STDIO and HTTP connection errors

Apply rapport-based elicitation to resistant or semi-cooperative humans and agents. Use when coercive prompting or brittle handoffs damage cooperation. NOT for routine cooperative tasks, pure technical debugging, or already reliable exchanges.

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

Structured interview and observation techniques for extracting tacit knowledge from domain experts

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

ALWAYS use this skill whenever you would otherwise ask the user a question in free-form chat -- for clarifications, confirmations (especially destructive actions), missing parameters, multiple-choice decisions, or structured form input. Elicitations are routed through the Unique AI Platform UI via `unique-cli elicit create` + `elicit wait` (the default polling pattern) or a single supervised `unique-cli elicit ask` call (only when your agent instructions say your environment supervises the wait) so the user gets a proper structured prompt and you get a structured answer back. Do NOT ask the user in plain chat when you can use this skill instead.

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

Structured interview and observation techniques for extracting tacit knowledge from domain experts

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

Apply rapport-based elicitation to resistant or semi-cooperative humans and agents. Use when coercive prompting or brittle handoffs damage cooperation. NOT for routine cooperative tasks, pure technical debugging, or already reliable exchanges.

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

Apply rapport-based elicitation to resistant or semi-cooperative humans and agents. Use when coercive prompting or brittle handoffs damage cooperation. NOT for routine cooperative tasks, pure technical debugging, or already reliable exchanges.

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

Revisit a recent answer, plan, draft, or decision using selected critique methods. The skill offers relevant approaches, explains what they reveal, and proposes improvements that are applied only after the user accepts them.

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

• Examining assumptions in a plan
• Reviewing a draft from several perspectives
• Exploring failure risks before a launch

Develop Bayesian models for quantitative social science, from choosing priors to reporting posterior results. Guide MCMC, a sampling method for estimating distributions, check convergence, and assess sensitivity for hierarchical models and small datasets.

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

• Choosing priors for models with small datasets
• Implementing hierarchical models in Stan or PyMC
• Investigating MCMC convergence problems

Build and evaluate Bayesian models with PyMC and ArviZ, from choosing initial assumptions to checking predictions. The workflow covers sampling diagnostics, model comparison, and reports that explain results with uncertainty intervals.

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

• Choose and check prior distributions
• Investigate sampling and convergence problems
• Compare hierarchical or regression models

Diagnose Codex behavior within BB, including question cards, MCP requests for user input or approval, Computer Use app access, model availability, service tiers, session options, and persistent goals, using thread and provider controls.

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

• Investigate a Codex turn waiting for an answer
• Review app access and MCP tool approvals
• Check models and service tiers on the execution host

Build MCP servers using the Leanmcp SDK with decorator-based TypeScript. Use this skill when users ask for "leanmcp", "MCP with decorators", "MCP with authentication", "MCP with elicitation", "MCP with environment injection", or want a simpler, more elegant way to build MCP servers. Leanmcp provides automatic schema generation, dependency injection, authentication, and user input collection.

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

Interactive PM interview with expertise-adaptive questioning for requirements elicitation

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

Authors Vally conformance tests for prompts, instructions, agents, and skills, and refuses jailbreak, prompt-injection, harmful-elicitation, TOS, CoC, and PII-extraction stimuli

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

Structured requirements elicitation for analysis requests. Use when scoping new analysis projects, clarifying ambiguous business questions, or documenting analysis acceptance criteria with stakeholders.

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

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team

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

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

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

Business Analyst agent. Use when starting a new feature requiring requirements elicitation BEFORE plan or cook. Asks probing questions, identifies hidden requirements, maps stakeholders, defines scope boundaries, and produces a structured Requirements Document that plan and cook consume.

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

Engineering design cycle covering requirements elicitation, specifications writing, constraint identification, iterative prototyping, and design communication. Spans the full loop from problem definition through ideation, analysis, prototyping, testing, and redesign. Includes morphological charts, TRIZ, Pugh matrices, design reviews, and the distinction between functional and non-functional requirements. Use when framing engineering problems, generating design alternatives, writing specifications, or running design reviews.

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

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team

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

Use when you want to improve response quality through meta-cognitive reasoning. Applies 15+ reasoning methods to reconsider and refine initial outputs.

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

Elicit and challenge data-analysis requirements before querying. Use when the user asks ambiguous data questions, requests business/report answers, needs metric definitions clarified, or may be drawing decisions from incomplete data.

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