gsd:spec-phase
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 skills add davepoon/buildwithclaude --skill spec-phase --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<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
What does the gsd:spec-phase skill do?
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.
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill spec-phase --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.