speckit-clarify

Ask up to five targeted questions to clarify underspecified feature specs.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/daksh7011/immich-backup --skill speckit-clarify-daksh7011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/daksh7011/immich-backup/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/daksh7011/immich-backup --skill speckit-clarify-daksh7011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Detect ambiguity early in the spec drafting process.
  • Generate concise, actionable clarification questions tailored to the spec.
  • Record verified clarifications directly in the spec file for traceability and future audits.

Quick Start

Start a clarification session on the active spec to generate and record up to 5 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 ambiguity in a feature spec before planning?

To identify ambiguity in a feature spec before planning, generate up to 5 targeted clarification questions that detect underspecified areas, then encode the answers directly back into the spec file to reduce downstream rework.

What is the best way to add clarification questions to a spec-kit workflow?

The best way to add clarification questions to a spec-kit workflow is running a clarification session that asks up to 5 tailored questions and records verified answers directly in the active spec for traceability and future audits.

Does spec clarification work with standard spec-kit project structures?

Spec clarification works with standard spec-kit project structures that include a .specify/ directory, operating specifically before any planning phase to minimize rework and maintain workflow adherence.

How many clarification questions can I generate for a feature spec?

You can generate up to 5 targeted, actionable clarification questions for a feature spec to effectively detect ambiguity early in the drafting process without overwhelming the review cycle.

Why should I clarify requirements before starting the planning phase?

You should clarify requirements before starting the planning phase to minimize downstream rework by resolving underspecified areas early and encoding verified traceability details directly into the spec.