skills.rest
yusaduymaz
yusaduymazCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gsd-spec-phase

Clarify phase requirements through iterative interviews and ambiguity scoring.

Updated May 22, 2026
Search Tags:#planning#specification#requirements#ambiguity#socratic questioning#workflows
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-spec-phase-yusaduymaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-spec-phase
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-spec-phase
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-spec-phase-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams clarify what a project phase must deliver before implementation starts, reducing ambiguity and preventing premature design or execution.

Core Features & Use Cases

  • Structured Requirement Clarification: Guides a Socratic interview loop to uncover missing details and surface hidden assumptions.
  • Ambiguity Scoring and Gating: Measures uncertainty across multiple dimensions and only proceeds when requirements are sufficiently clear.
  • SPEC.md Output: Produces a falsifiable phase specification with boundaries and acceptance criteria that downstream planning can rely on.

Quick Start

Ask the assistant to run the gsd-spec-phase workflow for a chosen phase and produce a SPEC.md before discuss-phase begins.

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 requirements before starting implementation?▼

Resolve ambiguity in software specifications by applying weighted ambiguity scoring across multiple dimensions. This process measures uncertainty and gates progress, only proceeding when requirements are sufficiently clear for implementation.

How do I create a falsifiable specification with acceptance criteria?▼

Create a falsifiable specification by generating a SPEC.md artifact through iterative interview rounds. This document captures explicit boundaries, falsifiable requirements, and acceptance criteria that downstream planning can rely on.

What is the best way to scope a project phase and resolve stakeholder ambiguity?▼

The best way to scope a project phase is through structured discovery using Socratic questioning and decision gating. This approach guides stakeholder interviews to resolve ambiguity and locks phase scope before planning.

Can I use ambiguity scoring to gate software development workflows?▼

This approach suits software projects needing structured discovery for a specific phase. It requires iterative interview rounds with stakeholders and produces a specification artifact capturing falsifiable requirements and explicit boundaries.

Why does premature design happen and how do I prevent it?▼

Premature design happens when phase requirements lack clarity and hidden assumptions remain. Prevent it by locking phase scope through Socratic questioning and producing a specification artifact with explicit boundaries before planning begins.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
FerroxLabsFerroxLabs
21

ferrox-spec-phase

Clarify ambiguous phase requirements and generate a SPEC.md with acceptance criteria.

Community
Advanced
misadecastromisadecastro

speckit-implement

Execute tasks.md-driven implementation plans with dependency and parallel-task rules.

Community
Advanced
calcosmiccalcosmic
9

spec-refinement

Refine ambiguous phase descriptions into falsifiable specifications with SPEC.md generation.

Community
Advanced