gsd-spec-phase

Generate a scope-bound SPEC.md with acceptance criteria and readiness gating.

4|Updated Apr 11, 2026

Search Tags:#workflow #planning #specification #requirements #ambiguity #phase

Ready to run

npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-spec-phase-electroheadfx

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn an unclear project phase into a precise specification by surfacing ambiguity, asking targeted questions, and locking down what the phase must deliver before planning begins.

Core Features & Use Cases

Socratic clarification: Guides structured questioning to expose missing requirements and hidden assumptions.
Ambiguity scoring: Quantifies uncertainty across multiple dimensions so you know when the phase is ready to move forward.
SPEC.md generation: Produces a falsifiable specification that defines scope, boundaries, and acceptance criteria for the next workflow stage.
Use case: Use it when a project has a rough idea of outcomes but needs a disciplined spec before design or implementation work starts.

Quick Start

Run the gsd-spec-phase skill with your phase number and any relevant context so it can ask the right questions and produce a SPEC.md.

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 project phase requirements before planning begins?▼

Clarifying project phase requirements involves using Socratic questioning to expose hidden assumptions and missing requirements, generating a scope-bound specification with explicit boundaries and acceptance criteria to gate readiness for the next phase.

What is the best way to write a specification for incomplete or contested project requirements?▼

Writing a specification for incomplete requirements involves quantifying ambiguity across multiple dimensions through structured questioning, producing a falsifiable SPEC.md that defines exact scope, boundaries, and acceptance criteria for your next workflow stage.

When do I need to generate a SPEC.md for a staged project workflow?▼

You need to generate a SPEC.md when a project phase has a rough idea of outcomes but lacks disciplined scope, or when requirements are incomplete, contested, or require validation before execution and design work can safely start.

How do I know if my project phase is ready to move to the next stage?▼

Readiness to move to the next stage is determined by ambiguity scoring, which quantifies uncertainty across multiple dimensions, ensuring missing requirements are resolved and explicit acceptance criteria are met before phase execution begins.

Can I use structured questioning to expose hidden assumptions in software planning?▼

Structured Socratic questioning exposes hidden assumptions in software planning by guiding targeted questions against incomplete requirements, validating contested scope boundaries, and locking down exact phase deliverables before generating a falsifiable specification.