speckit-clarify

Identify underspecified areas in feature specs and encode answers back into the spec.

10|3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/raphaelfh/newsweep --skill speckit-clarify-raphaelfh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/raphaelfh/newsweep/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/raphaelfh/newsweep --skill speckit-clarify-raphaelfh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

  • Interactive clarification session with up to 5 questions.
  • Taxonomy-based ambiguity coverage and prioritization.
  • Automatic updates to a Clarifications section in the spec with session-based bullets.
  • Incremental integration of accepted answers into functional spec sections.

Quick Start

Initiate a clarification session against the active feature spec to identify underspecified areas and commit answers back into the spec.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify ambiguity in a feature specification?

Clarify ambiguity in a feature specification by initiating an interactive session that asks up to five targeted questions, then encodes your answers back into the spec. This ensures underspecified areas are resolved directly within the document.

How do I resolve underspecified areas in a spec-kit project?

Resolve underspecified areas in a spec-kit project by using a guided workflow that prompts you with single questions and automatically updates a Clarifications section in the spec after each answer to improve planning fidelity.

Does spec-kit clarification work with existing functional spec sections?

Yes, spec-kit clarification works with existing functional spec sections by incrementally integrating accepted answers. It requires a .specify/ directory in your project to drive planning and implementation fidelity.

What is the best way to document product specification clarifications?

Document product specification clarifications by using taxonomy-based ambiguity coverage to prioritize questions, then automatically appending session-based bullets to a dedicated Clarifications section in the spec file.

Can I limit the number of clarification questions asked during a spec review?

Yes, you can limit clarification questions because the interactive session asks a maximum of five highly targeted questions. This prevents overwhelming the reviewer while covering critical underspecified areas.

When should I not use automated spec clarification?

You should not use automated spec clarification if your project lacks a .specify/ directory, as the tool relies on this structure to identify underspecified areas and commit session-based answers back into the spec.