spec-first-interview

Clarify ambiguous requests and generate immutable YAML seed specifications with acceptance criteria.

23|4|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/marlandoj/zouroboros --skill spec-first-interview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-first-interview
Source: https://github.com/marlandoj/zouroboros/tree/main/packages/workflow/docs/spec-first-interview
Command: npx skills add https://github.com/marlandoj/zouroboros --skill spec-first-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts ambiguous or underspecified requests into a clear, machine-readable specification to prevent wasted implementation effort, reduce misalignment across personas, and enforce acceptance criteria before development begins.

Core Features & Use Cases

  • Socratic Interviewing: Conduct a structured question-driven interview that isolates goals, constraints, and success criteria while always probing with follow-up questions.
  • Ambiguity Scoring & Gating: Quantify goal, constraint, and success clarity into an ambiguity score and gate seed generation until clarity thresholds are met.
  • Seed Generation & Ontology: Produce an immutable YAML seed containing goal, constraints, acceptance criteria, ontology, evaluation principles, and exit conditions; optionally run an ontologist lens and post-implementation gap audit.
  • Use Case: Use before building a new feature, multi-agent workflow, or cross-team integration to ensure requirements are explicit and testable.

Quick Start

Run a Socratic interview to clarify "Build a webhook retry system" and generate a seed YAML with goal, constraints, ontology, and acceptance criteria.

Frequently Asked Questions about spec-first-interview

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

FAQPage Schema
How do I turn vague project requests into clear acceptance criteria?

Ambiguity scoring quantifies the clarity of your project goals, constraints, and success criteria into a measurable score. This score gates seed generation, preventing specification output until clarity thresholds are met.

What is an immutable seed specification in requirements planning?

An immutable seed specification is a YAML file containing your project goal, constraints, ontology, acceptance criteria, and evaluation principles. It provides a fixed, machine-readable baseline to prevent wasted implementation effort.

When do I need to run a Socratic interview for project requirements?

An immutable seed specification is a YAML file containing your project goal, constraints, ontology, acceptance criteria, and evaluation principles. It provides a fixed, machine-readable baseline to prevent wasted implementation effort.

How do I generate a YAML seed specification for feature planning?

You need a Socratic interview for requirements when handling pre-implementation planning for multi-step builds, cross-persona projects, or vague tickets. It enforces explicit goals through structured, question-driven probing.

Does gap audit support post-implementation requirements verification?

You generate a YAML seed specification by completing a structured interview that clarifies your request. The output includes your goal, constraints, ontology, evaluation principles, and exit conditions for development readiness.

Can I use ontology mapping for cross-team integration requirements?

Yes, gap audit supports post-implementation verification by comparing the delivered output against your original immutable seed specification. This identifies missing functionality and enforces acceptance criteria alignment.