agentleFS
Sign inStart free
sp1esp1e/claude-skills/gsd-spec-phase/SKILL.md

gsd-spec-phase

Skill1 starsChanged 31 days agoMITView on GitHub

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

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 4 are common, 0 are distinctive, and 1 is very specific to this project.

  • 4

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Run Socratic interview loop (up to 6 rounds, rotating perspectives)

    line 24
  2. Common:

    Commit SPEC.md — discuss-phase picks it up automatically on next run

    line 27
  3. Very specific:

    Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion.

    line 38
  4. Common:

    MANDATORY: Read the workflow file BEFORE taking any action.

    line 54
  5. Common:

    All 4 ambiguity dimensions scored after each interview round

    line 59

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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: {phase_dir}/{padded_phase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how" </objective>

<execution_context> @$HOME/.claude/get-shit-done/workflows/spec-phase.md @$HOME/.claude/get-shit-done/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>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free