speckit-clarify

Identify underspecified areas in feature specs and propose up to five clarification questions.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-clarify-nalthoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/nalthoff/spec-kit-prep-specify/tree/main/.cursor/skills/speckit-clarify
Command: npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-clarify-nalthoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies underspecified areas in the current feature specification and prompts for focused clarifications, reducing rework and guiding accurate implementation.

Core Features & Use Cases

  • Up to 5 targeted questions surface gaps in the spec
  • Inline updates to the spec under a Clarifications section after each answer
  • Iterative, atomic writes ensure traceability and minimal drift

Quick Start

Run speckit-clarify on the active spec to surface up to five targeted questions.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify ambiguities in a software feature specification?

To identify ambiguities in a feature specification, analyze functional requirements, user roles, data models, edge cases, and integration points to surface underspecified areas and generate targeted clarification questions.

How do I write effective clarification questions for project requirements?

Write effective clarification questions by focusing on concise, verifiable queries that target underspecified areas like non-functional constraints and data models, ensuring answers can be directly applied to the next implementation phase.

What is the best way to reduce rework caused by underspecified requirements?

The best way to reduce rework from underspecified requirements is to surface up to five targeted clarification questions before implementation, encoding accepted answers directly back into the spec for traceability.

Can I update a specification iteratively as requirements are clarified?

Yes, you can update a specification iteratively by applying atomic writes to a Clarifications section after each accepted answer, ensuring minimal drift and maintaining traceability throughout the process.

What areas of a feature spec should I review for missing requirements?

Review functional requirements, user roles, data models, non-functional constraints, edge cases, and integration points to find missing requirements and ensure comprehensive feature specification coverage.

Does speckit-clarify support encoding clarification answers directly into the spec?

Yes, speckit-clarify supports encoding clarification answers directly into the spec by applying iterative, atomic writes to a dedicated Clarifications section after each answer is accepted.