Generate clarifying questions for underspecified feature specs in .specify/.
npx skills add https://github.com/ghbvf/gocell --skill speckit-clarify-ghbvf
Please help me install this Agent Skill. Skill: speckit-clarify Source: https://github.com/ghbvf/gocell/tree/main/.claude/skills/speckit-clarify Command: npx skills add https://github.com/ghbvf/gocell --skill speckit-clarify-ghbvf
This Skill identifies underspecified areas in the current feature spec and generates a concise set of clarifying questions to resolve ambiguities before planning and implementation. The questions help ensure complete requirements, reduce rework, and guide decision-making.
Run the clarifying workflow on the active feature spec to begin collecting questions.
High-intent search queries and answers about installing and using this skill.
You can resolve ambiguities in feature requirements by running an interactive clarifying session that generates up to five targeted questions. The session captures your answers and incrementally updates the spec under a dedicated Clarifications section for traceability.
The best way to generate clarifying questions for acceptance criteria is to analyze the spec for underspecified areas and produce a focused, succinctly answerable set. This ensures complete requirements and reduces rework before planning begins.
You update a feature spec incrementally by adding accepted answers to a dedicated Clarifications section. This preserves traceability by ensuring each generated question and its clarification are captured directly within the existing specification document.
Yes, the clarifying workflow applies directly to feature specifications stored in the .specify/ directory. It processes the active spec file to detect ambiguities and guides an interactive session to refine requirements and implementation details.
You need to clarify feature requirements using targeted question generation when planning and implementation begin. Generating questions early resolves constraints, reduces rework, and ensures decision-making is guided by complete requirements before development starts.
ApothecaryManIdentify and resolve ambiguities in feature specifications through targeted clarification questions.
CAPHTECHIdentify specification ambiguities and formalize acceptance criteria in Given/When/Then format.
shaman007Identify and resolve ambiguities in feature specifications through structured questioning.
estaciolimaGenerate structured checklists to validate technical requirements from project documentation.
