deep-interview
From the author
Mathematically rigorous Socratic interview system that drives ambiguity below 20% before any code is written. One question per message, weighted ambiguity scoring, brownfield-aware, outputs a complete PRD. Replaces discovery-interview with a stricter protocol.
Install
npx skills add vibeeval/vibecosystem --skill deep-interview -a claude-code
Installs to .claude/skills/deep-interview/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 84
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- discovery-interviewparcadei/Continuous-Claude-v3Deep interview process to transform vague ideas into detailed specs. Works for technical and non-technical users.Planning★ 3.9K
- deep-diveJoonghyun-Lee-Frieren/oh-my-antigravityRun a trace-to-interview discovery pass to remove ambiguity before planning and execution.Planning★ 213
- adrbeevibe-ai/beevibe-ctoArchitecture Deep Research — scan the current repo, draft a PRD, and run the deep-research loop with citation audits. Use when the user asks you to make an architecture decision, asks "what topology should we use?", says they need to pick between options like vector stores / message queues / retrieval patterns / storage engines / event bus designs, or wants you to think through an architecture choice before writing code. Proactively invoke this skill (do NOT decide directly) when the user describes an architecture choice and wants live, cited research instead of a model-from-memory answer.Science★ 104
- interview-meaddyosmani/agent-skillsExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.Planning★ 110.1K
- gsd:spec-phasedavepoon/buildwithclaudeSocratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.Planning★ 3.7K
- oma-interviewJoonghyun-Lee-Frieren/oh-my-antigravityRun a Socratic Interview loop to clarify requirements, or manage interview sessions.Planning★ 213
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in