Resolve high-impact ambiguities in a feature specification and update spec.md.
npx skills add https://github.com/ahgraber/skills --skill spec-kit-clarify
Please help me install this Agent Skill. Skill: spec-kit-clarify Source: https://github.com/ahgraber/skills/tree/main/skills/spec-kit-clarify Command: npx skills add https://github.com/ahgraber/skills --skill spec-kit-clarify
Resolve high-impact ambiguities in an active feature specification before planning.
Initiate the clarify workflow to resolve ambiguities in spec.md before planning.
High-intent search queries and answers about installing and using this skill.
To resolve ambiguous specifications before planning, you can run a clarification workflow that identifies placeholders like NEEDS CLARIFICATION and updates spec.md with accepted answers to critical questions.
Specification clarification is a workflow that surfaces up to five high-impact questions to resolve unresolved scope decisions, ensuring unquantified requirements do not negatively affect architecture or data models.
You update spec.md with accepted answers by initiating an interactive clarification loop that integrates decisions directly into the document, implementing structured ambiguity tracking and traceability.
Yes, you can use a structured workflow to assess specification ambiguity by evaluating unquantified requirements that affect validation, data models, or architecture, and tracking them for resolution.
A limitation of resolving ambiguities in feature specifications is that the workflow surfaces a maximum of five critical questions, prioritizing only unresolved scope decisions that could impact architecture or validation.
whatwecandoConvert an initial idea into a structured BLUEPRINT.md draft through guided dialogue.
juvenalScan feature specifications for gaps and generate prioritized clarification questions.
zircoteCreate and manage multiple Git worktrees with a global JSON registry.
patrickrmooreGuide targeted questions to clarify specs and record answers into spec.md.
