From 738494b1aa02a7874f7ae4672247fd3dfe359cb4 Mon Sep 17 00:00:00 2001 From: Eray Date: Mon, 12 Jan 2026 00:34:45 +0300 Subject: [PATCH] Add @tibo-openai's ask-questions-if-underspecified skill --- .../ask-questions-if-underspecified/SKILL.md | 59 +++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 skills/.experimental/ask-questions-if-underspecified/SKILL.md diff --git a/skills/.experimental/ask-questions-if-underspecified/SKILL.md b/skills/.experimental/ask-questions-if-underspecified/SKILL.md new file mode 100644 index 00000000..38d1e0b9 --- /dev/null +++ b/skills/.experimental/ask-questions-if-underspecified/SKILL.md @@ -0,0 +1,59 @@ +--- +name: ask-questions-if-underspecified +description: Clarify requirements before implementing changes or plans when a request is underspecified. Use when objectives, scope, constraints, acceptance criteria, or environment details are unclear and you need the minimum set of questions before proceeding. +--- + +# Ask Questions If Underspecified + +## Goal + +Ask the minimum set of clarifying questions needed to avoid wrong work. Do not begin implementation until must-have answers are provided or the user explicitly approves stated assumptions. + +## Workflow + +1) Decide whether the request is underspecified +- Check objective (what should change vs stay the same) +- Check done criteria (acceptance, examples, edge cases) +- Check scope (files/components/users in or out) +- Check constraints (compatibility, performance, style, deps, time) +- Check environment (language/runtime versions, OS, test runner) +- Check safety/reversibility (migrations, rollout, risk) + +2) Ask must-have questions first +- Ask 1 to 5 questions that remove whole branches of work +- Use numbered questions with short options (a/b/c) +- Provide a clear default (bold it) and a fast path reply like "defaults" +- Allow "not sure - use default" when helpful +- Separate "Need to know" from "Nice to know" only if it reduces friction + +3) Pause before acting +- Do not run commands, edit files, or make a detailed plan that depends on missing info +- A low-risk discovery read is allowed if it does not commit to a direction + +4) Confirm and proceed +- Restate requirements and success criteria in 1 to 3 sentences +- Begin work only after answers or explicit approval of assumptions + +## Response format + +Use a compact, scannable structure. Example: + +```text +Need to know +1) Scope? + a) **Minimal change** + b) Refactor while touching the area + c) Not sure - use default +2) Compatibility target? + a) **Current project defaults** + b) Also support older versions: + c) Not sure - use default + +Reply with: defaults (or 1a 2a) +``` + +## If asked to proceed without answers + +- State assumptions as a short numbered list +- Ask for confirmation +- Proceed only after confirmation or corrections