open-gsd/gsd-core

gsd-spec-phase

Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.

First seen Jun 23, 2026

Installation

$ npx skills add open-gsd/gsd-core --skill gsd-spec-phase

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from open-gsd/gsd-core · top by installs.

npx skills add open-gsd/gsd-core

Browse all from open-gsd/gsd-core

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 9.3K
License LICENSE
Default branch next
Open issues 129
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Bash, Glob, Grep, AskUserQuestion
Declared agents claude-code github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,440 B
  • docs SUMMARY.md 113 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 252 installs

SKILL.md

<objective> Clarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.

Position in workflow: spec-phase → discuss-phase → plan-phase → execute-phase → verify

How it works:

  1. Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
  2. Scout the codebase — understand current state before asking questions
  3. Run Socratic interview loop (up to 6 rounds, rotating perspectives)
  4. Score ambiguity across 4 weighted dimensions after each round
  5. Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
  6. Commit SPEC.md — discuss-phase picks it up automatically on next run

Output: {phasedir}/{paddedphase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how" </objective>

<executioncontext> @~/.claude/gsd-core/workflows/spec-phase.md @~/.claude/gsd-core/templates/spec.md </executioncontext>

<runtimenote> Copilot (VS Code): Use vscodeaskquestions wherever this workflow calls AskUserQuestion. They are equivalent. </runtime_note>

<context> Phase number: $ARGUMENTS (required)

Flags:

  • --auto — Skip interactive questions; Claude selects recommended defaults and writes SPEC.md
  • --text — Use plain-text numbered lists instead of TUI menus (required for /rc remote sessions)

Context files are resolved in-workflow using init phase-op. </context>

<process> Execute end-to-end.

MANDATORY: Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above. </process>

<success_criteria>

  • Codebase scouted for current state before questioning begins
  • All 4 ambiguity dimensions scored after each interview round
  • Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met
  • SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria
  • SPEC.md committed atomically
  • User knows they can now run /gsd-discuss-phase which will load SPEC.md automatically

</success_criteria>