skills/spec-phase/SKILL.md
Socratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.
npx skillsauth add jnuyens/gsd-plugin gsd:spec-phaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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"
</objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/spec-phase.md @${CLAUDE_PLUGIN_ROOT}/templates/spec.md </execution_context>
<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>
MANDATORY: Read the workflow file BEFORE taking any action. Do not improvise from the objective summary above. </process>
<success_criteria>
tools
Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.
tools
Schedule a future resume of work - e.g. '/gsd:resume-at 09:00', '/gsd:resume-at +2h', or '/gsd:resume-at 04:00 --cmd /gsd:execute-phase 9'
tools
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
tools
Manage persistent context threads for cross-session work