Clarify vague requests through Socratic interviews into execution-ready specifications.
npx skills add https://github.com/pextacy/stellar --skill deep-interview-pextacy
Please help me install this Agent Skill. Skill: deep-interview Source: https://github.com/pextacy/stellar/tree/main/skills/deep-interview Command: npx skills add https://github.com/pextacy/stellar --skill deep-interview-pextacy
Deep Interview provides an intent-first Socratic clarification loop that turns vague ideas into execution-ready specifications by probing why, how far, and what should stay out of scope, reducing misalignment before planning or implementation.
Provide a vague idea and let Deep Interview extract a concrete, testable spec through iterative Socratic questioning.
High-intent search queries and answers about installing and using this skill.
To clarify vague project requirements, you can use an intent-first Socratic clarification loop that probes priorities and constraints, turning ambiguous ideas into execution-ready specifications with explicit acceptance criteria. This reduces misalignment before planning.
A Socratic interview for requirements gathering is a guided questioning process that surfaces decision boundaries and non-goals. You should use it when user requests are ambiguous or under-specified to ensure alignment before implementation begins.
Yes, you can configure the clarification process depth using Quick, Standard, Deep, and Autoresearch profiles. These modes match project rigor and launch readiness, allowing you to control the intensity of the Socratic interview.
The best way to extract non-goals and decision boundaries from stakeholder ideas is through a context-aware Socratic interview that applies readiness gates, tightening scope by explicitly defining what stays out of bounds and what constitutes acceptance.
Yes, this requirements clarification approach generates structured artifacts and context intake outputs designed for handoff readiness. It produces execution-ready specifications directly compatible with downstream planning and execution tools.
You should not use a Socratic interview for requirements planning when a project scope is already tightly defined, acceptance criteria are fully established, and no ambiguity exists among stakeholders, as the questioning loop would add unnecessary overhead.
jetmobsolAnalyze user requests to detect intent, type, complexity, and vague terms.
jfrometaClarify vague product and feature requests through Socratic questioning.
bowiemaxGenerate a stakeholder map and communication plan using a power/interest grid.
BetaSGather requirements through a structured Socratic clarification loop.
