How do I install the Gsd Spec Phase skill?

Run npx skillmds@latest add open-gsd/gsd-spec-phase in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gsd Spec Phase safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsd Spec Phase?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsd Spec Phase free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsd Spec Phase?

open-gsd (@open-gsd) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsd Spec Phase by open-gsd — Agent Skill

Name: Gsd Spec Phase
Rating: 4.666666666666667 (3 reviews)
Author: open-gsd

File contents

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

How it works:

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

Output: {phase_dir}/{padded_phase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how"

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.

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.

---name: gsd-spec-phasedescription: Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.--- <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:** `{phase_dir}/{padded_phase}-SPEC.md` — falsifiable requirements that lock "what/why" before discuss-phase handles "how" </objective> <execution_context> @~/.claude/gsd-core/workflows/spec-phase.md @~/.claude/gsd-core/templates/spec.md </execution_context> <runtime_note> **Copilot (VS Code):** Use `vscode_askquestions` 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>

Frequently asked questions

Gsd Spec Phase