questioning

Solid

Ask targeted clarification questions only when high-impact unknowns block safe execution.

AI & Automation 295 stars 57 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 93/100

Stars 20%
82
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
35
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<questioning> <role> You are a clarification specialist for execution blockers. </role> <when_to_use_skill> Use when critical or high unknowns affect scope, security, UX, or technical delivery and planning cannot continue safely without decisions. Output contains targeted questions with impact and safe defaults. </when_to_use_skill> <rules> - Ask only critical/high-impact questions. - Prioritize by impact: scope > security/privacy > UX > technical. - Ask 5-10 questions only when unknowns exist. - Keep one decision per question. - Include why it matters and safe default. - Track open questions with todo tasks. - STOP when critical blockers remain unresolved. </rules> </questioning>

Details

Author
griddynamics
Repository
griddynamics/rosetta
Created
4 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

ask-questions-if-underspecified

Use this skill when scope ambiguity blocks progress in any SOP step (PRD, TDD, design, task decomposition). Produces a tight set of clarifying questions (max 5) that, once answered, unblock the next step. Avoids the failure mode where Agents proceed on assumption and produce wrong work. Chinese trigger examples: "需求不清", "需要澄清", "提问澄清", "范围不明", "信息不足要澄清", "ask the user". Do NOT use for exploration (use research), do NOT use to delay obvious work. Success = ≤ 5 questions, each decision-shaping, each tied to a specific PRD section.

101 Updated 1 weeks ago
charliehzm
AI & Automation Listed

ask-me-questions

Systematic requirements discovery through multi-round questioning before taking action. Use when the user explicitly asks — "ask me questions", "ask me first", "interview me", "gather requirements", "understand what I need" — or when a request is genuinely ambiguous: multiple plausible interpretations leading to materially different implementations, and the right one isn't discoverable from the code or context. Do NOT use for clear requests, however large.

0 Updated yesterday
nsollazzo
AI & Automation Solid

ask-questions-if-underspecified

Clarify requirements before implementing. Use when serious doubts arise.

40,440 Updated today
sickn33