skills.rest
riethmayer
riethmayerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

deep-interview

Guide users through structured Socratic interviews to turn vague ideas into execution-ready specifications.

2|1|Updated Oct 8, 2009
Search Tags:#planning#requirements#clarification#interview#socratic#artifact#omx
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill deep-interview-riethmayer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-interview
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/deep-interview
Command: npx skills add https://github.com/riethmayer/dotfiles --skill deep-interview-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts vague or broad requests into precise, testable requirements by guiding users through a structured, Socratic clarification process before planning or execution.

Core Features & Use Cases

  • Interactive clarification loop that probes intent, outcomes, scope, constraints, and acceptance criteria.
  • Supports phases for planning handoffs to downstream tools like ralplan, autopilot, ralph, or team with explicit non-goals and decision boundaries.
  • Provides artifact persistence (context snapshots and interview transcripts) for traceability and reuse in future work.

Quick Start

Provide a vague idea and run the deep-interview with a chosen depth profile to generate a concrete, execution-ready specification.

Frequently Asked Questions about deep-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague project ideas into execution-ready specifications?▼

A Socratic clarification interview converts ambiguous requests into precise, testable specifications by guiding users to define intent, outcomes, scope, and acceptance criteria through a structured questioning process.

What is the best way to clarify requirements for broad project requests?▼

The best way to clarify broad project requests is through an interactive clarification loop that enforces a one-question-per-round cadence, ensuring all constraints and non-goals are explicitly defined before downstream execution.

How does a Socratic interview handle brownfield context for requirement gathering?▼

Socratic requirement gathering handles brownfield scenarios by applying context grounding, ensuring existing project constraints are acknowledged before defining new decision boundaries and acceptance criteria.

Can I persist clarification interview transcripts for future project reuse?▼

Yes, you can persist clarification interview transcripts by saving context snapshots and artifacts to .omx contexts, providing traceability and enabling reuse for future planning work.

When should I use a structured clarification process instead of direct project planning?▼

You should use a structured clarification process when requests are broad or ambiguous, as it enforces explicit readiness gates like non-goals and decision boundaries before handing off to downstream planning tools.

Related Skills

Explore More Product & Management Skills→
lpjhelderlpjhelder

deep-interview

Clarify vague project ideas through Socratic interviews and generate specs in .forge.

Community
Advanced
INNERJOINTINNERJOINT

deep-dive

Trace root causes and produce interview-driven specifications for downstream planning.

Community
Advanced
u9401066u9401066

roadmap-updater

Update ROADMAP.md statuses from commits during git workflows.

Community
Basic
BetaSBetaS

deep-interview

Gather requirements through a structured Socratic clarification loop.

Community
Advanced