skills.rest
tinner-deinno
tinner-deinnoCOMMUNITY
Explore all skills by this author →
GitHub

gsd-spec-phase

Generates SPEC.md from Socratic interviews with quantitative ambiguity scoring.

1|Updated May 24, 2026
Search Tags:#specification#requirements#socratic questioning#workflow planning#phase execution#codebase scouting#ambiguity scoring
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-spec-phase-tinner-deinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-spec-phase
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-spec-phase
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-spec-phase-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces uncertainty in planning by clarifying exactly what a phase must deliver, using structured questions and measurable ambiguity scoring.

Core Features & Use Cases

  • Socratic phase scoping: Runs an interview loop (up to 6 rounds) that rotates perspectives to uncover missing requirements and conflicting assumptions.
  • Quantitative ambiguity gating: Scores ambiguity across 4 weighted dimensions after each round and blocks output until the threshold is met.
  • Falsifiable SPEC output: Writes a SPEC.md with bounded “what/why” requirements so the next phase can focus on “how”.
  • Typical use case: Before execution planning, you need requirements that stakeholders (and future automation) can validate against real codebase state.

Quick Start

Run gsd-spec-phase for the target phase and include --auto when you want recommended defaults to be selected and SPEC.md to be generated without interactive prompts.

Frequently Asked Questions about gsd-spec-phase

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

FAQPage Schema
How do I turn ambiguous project requirements into falsifiable specifications?▼

Ambiguity scoring evaluates clarity across four weighted dimensions after each interview round. It blocks specification output until the score drops to 0.20 or below with minimums met per dimension, ensuring fully bounded what and why requirements.

What's the best way to scope deliverables before execution planning?▼

The best way to scope deliverables before execution planning is running a Socratic interview loop of up to six rounds to clarify phase goals, producing a locked SPEC.md with falsifiable requirements for downstream planning phases.

Can I automatically generate a SPEC.md without interactive prompts?▼

Yes, you can automatically generate a SPEC.md without interactive prompts by running the phase scoping process with the auto flag enabled, which selects recommended defaults and outputs the specification file directly.

Why do I need codebase scouting before locking workflow specifications?▼

Codebase scouting is needed before locking workflow specifications because it gathers the current codebase state, ensuring the generated SPEC.md contains requirements that stakeholders and automation can validate against actual project conditions.

How does Socratic questioning improve workflow planning for software phases?▼

Socratic questioning improves workflow planning by rotating perspectives across up to six interview rounds to expose conflicting assumptions and missing requirements, reducing uncertainty before execution planning begins.

Related Skills

Explore More Product & Management Skills→
ZJUxjyZJUxjy

receiving-code-review

Analyze and verify code review feedback for technical accuracy before implementation.

Community
Intermediate
hadpadrahulhadpadrahul

gsd-spec-phase

Generate a locked SPEC.md through structured Socratic questioning and ambiguity scoring.

Community
Advanced
abrahamgreysonabrahamgreyson

gsd:reference:continuation-format

Restore GSD session state and review checkpoints before resuming work.

Community
Basic
nnexainnexai
1

gsd-spec-phase

Clarifies project requirements via Socratic interviews and ambiguity scoring.

Community
Advanced