Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
$ARGUMENTS
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
Position in workflow: spec-phase → discuss-phase → plan-phase → execute-phase → verify
How it works:
Output: {phase_dir}/{padded_phase}-SPEC.md — falsifiable requirements that lock "what/why" before discuss-phase handles "how"
<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>
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.
<success_criteria>
open-gsd/gsd-core
99bbbac
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.