Scan feature specifications against a taxonomy and resolve ambiguities interactively.
npx skills add https://github.com/agol586/wb86 --skill speckit-clarify-agol586
Please help me install this Agent Skill. Skill: speckit-clarify Source: https://github.com/agol586/wb86/tree/main/.agents/skills/speckit-clarify Command: npx skills add https://github.com/agol586/wb86 --skill speckit-clarify-agol586
This Skill addresses the common issue of vague or incomplete feature specifications by identifying missing decision points and forcing structured resolution before implementation begins.
Invoke the speckit-clarify skill to scan the current feature specification and resolve any identified ambiguities through an interactive session.
High-intent search queries and answers about installing and using this skill.
To identify ambiguities in a feature specification, scan the document against a structured taxonomy to flag missing functional, non-functional, and edge-case requirements. This structured process ensures all decision points are captured and testable.
The best way to clarify missing requirements is through an interactive questioning loop that guides you through a prioritized list of critical uncertainties. This approach limits the session to five questions to resolve ambiguities efficiently without overwhelming the user.
Yes, specification clarification requires a project structure containing a .specify directory and a valid feature specification file. This setup allows the scanning process to locate and analyze the target document for missing decision points.
Ambiguity resolution updates the specification file through automated integration, immediately writing the clarified answers back into the source document. This ensures the specification remains the current source of truth for downstream planning and development.
You should scan a feature specification for edge-case requirements during the planning phase, before implementation begins. Resolving these critical uncertainties early ensures the requirements are testable, complete, and ready for software development workflows.
PiklarIdentifies specification ambiguities and resolves them via interactive clarification workflow.
pradeepmouliClarify underspecified feature requirements through an interactive five-question loop.
BrennonTWilliamsExecute linting, formatting, and type checking on project code.
EarthmanWebExtract explicit and implicit requirements from user requests into WORKING_MEMORY.
