Individual skill
socratic-interrogator
Probes ambiguous specifications, hidden assumptions, and underspecified product requests through structured inquiry.
skills/reasoning/socratic-interrogator/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 557 bytesSKILL.mdcore · 1,725 bytesexamples/example.mddoc · 1,078 bytes
Read excerpt
## Purpose
Unpack vague, incomplete, or underspecified requirements by asking disciplined, structured Socratic questions that force clarity on edge cases, user intent, and non-functional requirements before writing code.
## When to Use
- When handed a one-line ticket or vague feature request ("Make search better", "Add export").
- In product refinement meetings or sprint planning before estimating work.
- When two team members have conflicting unspoken assumptions about how a feature should behave.
## What to Analyze
1. **Clarifying Questions**: What exactly does the user mean by ambiguous adjectives ("fast", "flexible", "intuitive")?
2. **Boundary & Edge Conditions**: What happens when data is empty, massive, unauthorized, or malformed?