From gsd
Refines project phase specifications via Socratic questioning, ambiguity scoring across 4 dimensions, and gating to produce SPEC.md with falsifiable requirements before discuss-phase.
npx claudepluginhub jnuyens/gsd-plugin --plugin gsdThis skill is limited to using the following tools:
<objective>
Identifies underspecified areas in feature specs using a taxonomy of functional, data model, UX, non-functional, integrations, edge cases, and constraints. Asks up to 5 targeted questions and encodes answers back into the spec before planning.
Identifies underspecified areas in feature specs by asking up to 5 targeted clarification questions, logging answers, and updating the spec.
Identifies phase-specific gray areas and gathers implementation decisions through adaptive questioning, outputting CONTEXT.md to guide planning without further user input.
Share bugs, ideas, or general feedback.
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_PLUGIN_ROOT}/workflows/spec-phase.md @${CLAUDE_PLUGIN_ROOT}/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>