speckit-clarify

Identifies gaps in project specs and generates clarifying questions for missing details.

1|Updated Feb 23, 2026

Search Tags:#workflow #specification #requirements #clarification #ambiguity #spec-kit

Ready to run

npx skills add https://github.com/LISSConsulting/RalphSpec --skill speckit-clarify-lissconsulting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/LISSConsulting/RalphSpec/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/LISSConsulting/RalphSpec --skill speckit-clarify-lissconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires powershell, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses underspecified requirements by systematically identifying and resolving ambiguities through targeted questioning, ensuring clarity before implementation begins.

Core Features & Use Cases

Ambiguity Detection: Scans specifications for missing or unclear details across various categories like functional scope, data models, and non-functional attributes.
Structured Questioning: Engages users with focused, multiple-choice or short-answer questions to gather necessary clarifications.
Incremental Spec Updates: Integrates answers directly into the specification file, maintaining a clear audit trail.
Use Case: Before starting development on a new feature, run this Skill to ensure all user stories, data structures, and edge cases are clearly defined, preventing costly rework later.

Quick Start

Run the speckit-clarify skill to resolve any ambiguities in the current feature specification.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema

How do I resolve ambiguities in software requirements before implementation?▼

To resolve ambiguities in software requirements, you can use a structured clarification workflow that scans specifications for missing details across functional scope, data models, and edge cases, then generates targeted questions to ensure clarity before development begins.

What does ambiguity detection in a specification typically cover?▼

Ambiguity detection in a specification covers scanning for missing or unclear details across functional scope, data models, user interaction, non-functional attributes, and edge cases to ensure a testable definition of requirements.

How do I clarify underspecified user stories and data structures step by step?▼

You clarify underspecified user stories by running a workflow that identifies ambiguities, engages you with focused multiple-choice or short-answer questions, and incrementally records your answers directly into the specification file.

Do I need PowerShell to run the specification clarification workflow?▼

Yes, PowerShell is a required dependency to run the specification clarification workflow, which uses scripts to scan spec-kit project files and incrementally update them with your clarifications.

What is the best way to maintain an audit trail for requirement clarifications?▼

The best way to maintain an audit trail for requirement clarifications is to integrate answers directly into the specification file's clarifications section incrementally as they are provided, preserving a clear history of changes.

Why should I clarify requirements before planning or implementation?▼

You should clarify requirements before planning or implementation to prevent costly rework later, ensuring all user stories, data structures, and edge cases are clearly defined and testable before development starts.