alfredolopez80/ask-questions-if-underspecified
.claude/skills/ask-questions-if-underspecified/SKILL.md
Ask clarifying questions when requirements are underspecified
$ install --global
skillsauthnpx skillsauth add alfredolopez80/multi-agent-ralph-loop ask-questions-if-underspecifiedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 6:05 PM39.4s1 file scanned
SKILL.md
- # VERSION:
- 3.0.0
- name:
- ask-questions-if-underspecified
- description:
- Ask clarifying questions when requirements are underspecified
- user-invocable:
- true
Skill: Ask Questions If Underspecified
v2.88 Key Changes (MODEL-AGNOSTIC)
- Model-agnostic: Uses model configured in
~/.claude/settings.jsonor CLI/env vars - No flags required: Works with the configured default model
- Flexible: Works with GLM-5, Claude, Minimax, or any configured model
- Settings-driven: Model selection via
ANTHROPIC_DEFAULT_*_MODELenv vars
ultrathink - Take a deep breath. We're not here to write code. We're here to make a dent in the universe.
The Vision
Clarity is the foundation of inevitable solutions. Every question should narrow the path to truth.
Your Work, Step by Step
- Analyze requirements: Identify missing inputs and ambiguities.
- Separate MUST vs NICE: Block on essentials, assume the rest.
- Ask precisely: Short, concrete questions with defaults.
- Confirm understanding: Summarize before proceeding.
Ultrathink Principles in Practice
- Think Different: Question hidden assumptions.
- Obsess Over Details: Align questions with real constraints.
- Plan Like Da Vinci: Build the question set before asking.
- Craft, Don't Code: Precision over volume.
- Iterate Relentlessly: Refine questions as context evolves.
- Simplify Ruthlessly: Ask only what matters.
Purpose
Ensure task clarity BEFORE implementation by identifying ambiguities.
When to Use
- ANY new task or feature request
- Complex modifications
- Unclear requirements
Process
1. Analyze Requirements
Identify:
- Missing technical details
- Unclear scope boundaries
- Ambiguous terminology
- Unstated assumptions
2. Categorize Questions
MUST_HAVE (Blocking)
Questions that BLOCK implementation until answered:
- Critical architecture decisions
- Security requirements
- Data model choices
- Integration points
NICE_TO_HAVE (Assumptions)
Questions where you can make reasonable assumptions:
- UI/UX preferences
- Performance targets
- Edge case handling
3. Output Format
## 🔍 Clarification Needed
### MUST_HAVE (Please answer before I proceed):
1. [Critical question 1]
2. [Critical question 2]
### NICE_TO_HAVE (I'll assume these if not specified):
- [Optional question] → I'll assume: [default value]
- [Optional question] → I'll assume: [default value]
### My Understanding:
[Summarize what you understand so far]
4. Wait for Answers
DO NOT proceed with implementation until MUST_HAVE questions are answered.
Examples
Good Clarification
MUST_HAVE:
1. Should auth support both email/password AND OAuth providers?
2. What's the session timeout requirement?
NICE_TO_HAVE:
- Rate limiting? → I'll assume: 100 req/min
- Password complexity? → I'll assume: min 8 chars, 1 number, 1 special
Bad (Too Vague)
What do you want?
Can you give more details?
Related Skills
alfredolopez80/vault
development
VerifiedTrustedCommunity
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/spec
testing
VerifiedTrustedCommunity
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/ship
testing
VerifiedTrustedCommunity
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/perf
development
VerifiedTrustedCommunity
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.
121SKILL.mdUpdated Apr 15, 2026