gsd-spec-phase

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

Updated Apr 22, 2026

Search Tags:#automation #codebase #specification #ambiguity #socratic #phase-management

Ready to run

npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-spec-phase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-spec-phase
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-spec-phase
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-spec-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Socratic spec refinement helps teams clarify WHAT a phase delivers by scoring ambiguity before implementing discussions, ensuring a well-scoped SPEC.md is produced.

Core Features & Use Cases

Structured Socratic interview loops (up to six rounds) with perspective rotation to surface hidden assumptions.
Ambiguity scoring across four dimensions to drive objective gates before discuss-phase.
Automatic SPEC.md generation and atomic commit, ready for the next workflow step to load in the discuss-phase.

Quick Start

Invoke the spec-phase workflow with a phase identifier to start refinement and generate SPEC.md when gates are met.

Frequently Asked Questions about gsd-spec-phase

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

FAQPage Schema

How do I clarify phase deliverables and reduce ambiguity before implementation?▼

Phase spec refinement uses a structured Socratic questioning loop to surface hidden assumptions and score ambiguity across four dimensions, ensuring a well-scoped SPEC.md is produced before development begins.

What is the best way to generate a locked SPEC.md with falsifiable requirements?▼

Generating a locked SPEC.md involves orchestrating up to six Socratic interview rounds with perspective rotation, gating output generation on an ambiguity score, and committing the file atomically to preserve phase context.

How does Socratic specification phase management work during codebase scouting?▼

Socratic phase management works by loading phase context, scouting the codebase for existing patterns, running interview loops with perspective rotation, and gating SPEC.md generation until ambiguity drops below threshold limits.

Can I use Socratic spec refinement for an existing codebase with undefined phase boundaries?▼

Yes, Socratic spec refinement suits existing codebases by scouting current codebase structure to inform the interview loop, rotating perspectives across six rounds to expose hidden assumptions, and locking phase boundaries in SPEC.md.

Why does my phase specification lack falsifiable requirements for downstream workflows?▼

Phase specifications lack falsifiable requirements when ambiguity scoring gates are bypassed; running the full Socratic interview loop enforces objective scoring across four dimensions before generating a SPEC.md file.

What happens after the SPEC.md is generated and atomically committed?▼

After SPEC.md generation and atomic commit, a subsequent discuss-phase workflow can automatically load the locked SPEC.md file to begin implementation discussions using the refined, falsifiable requirements.