speckit-clarify

Identify and resolve ambiguities in feature specifications through targeted clarification questions.

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-clarify-apothecaryman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agent/skills/speckit-clarify
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-clarify-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spec-kit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies underspecified areas in feature specifications by asking targeted clarification questions and recording the answers directly back into the spec, reducing ambiguity and enhancing spec quality.

Core Features & Use Cases

  • Targeted Clarification: Asks up to 5 highly targeted questions to clarify underspecified areas.
  • Spec Integration: Encodes answers directly into the spec, improving accuracy and clarity.
  • Compatibility: Requires a spec-kit project structure with a .specify/ directory.
  • Use Case: When reviewing a feature spec for a software project, use this Skill to detect and address areas of ambiguity, such as missing decision points or unclear requirements, enhancing the spec before finalizing the plan.

Quick Start

To begin clarifying your spec, run the 'speckit-clarify' command in your project directory.

Frequently Asked Questions about speckit-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify ambiguities in a feature specification before finalizing the project plan?

Clarify feature specification ambiguities by running a structured questioning workflow that identifies underspecified areas, asks up to 5 targeted questions, and encodes your answers directly back into the spec documentation to reduce missing decision points.

Do I need a spec-kit project structure to use a specification clarification workflow?

Yes, specification clarification requires an existing spec-kit project structure containing a .specify/ directory to provide the necessary context for detecting ambiguities and writing refined spec documentation back into the project.

What is the best way to detect underspecified areas in software feature specs?

The best way to detect underspecified areas in feature specs is using structured ambiguity detection, which scans your specification and prompts you with targeted clarification questions to resolve unclear requirements before development.

How do I run the spec clarification process in my software development project?

Run the spec clarification process by executing the 'speckit-clarify' command in your project directory, which initiates the questioning workflow to identify ambiguities and refine your feature specification documentation.

Can I resolve missing decision points in feature specifications without manual review?

Resolving missing decision points requires user-driven clarification, where the workflow asks up to 5 targeted questions about ambiguities and you provide the answers that are then encoded directly into the feature specification.

What are the limitations of automated ambiguity detection in spec documentation?

Ambiguity detection is limited by its dependency on the spec-kit project structure and requires user-driven input to answer targeted questions, meaning it cannot autonomously resolve unclear requirements without human clarification decisions.