speckit-clarify

Generate targeted clarifying questions for feature specifications and commit answers.

Updated May 16, 2026
One-click install
npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-clarify-weihanli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/WeihanLi/Spark.OpenXml/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-clarify-weihanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguities in feature specifications slow delivery and risk misaligned implementations.

Core Features & Use Cases

  • Generate up to five highly targeted clarification questions to resolve gaps in the current spec.
  • Encode answers back into the spec under a dedicated Clarifications section with a date-stamped session.
  • Integrate with the spec workflow (.specify) and automatically validate prerequisite conditions.

Quick Start

Run the speckit-clarify workflow on the current spec and answer up to five questions to update 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 ambiguities in a feature specification?

You can clarify ambiguities in a feature specification by generating targeted clarifying questions to identify underspecified areas, then committing the answers back into the spec.

How do I add a clarifications section to my spec document?

To add a clarifications section to your spec document, run the clarify workflow to encode session answers into a dedicated, date-stamped section while preserving existing formatting.

How many clarifying questions can be generated per spec session?

You can generate up to five highly targeted clarifying questions per spec session to resolve gaps in your current specification without overwhelming the review process.

Does the specification clarification process preserve existing wording?

Yes, the specification clarification process preserves existing wording and formatting in your document while applying structured, testable updates and inline documentation to the spec.

What is the best way to find underspecified areas in requirements planning?

The best way to find underspecified areas in requirements planning is to use automated prerequisite checks that validate conditions and generate focused questions for missing specification details.

Can I use this for automated spec workflow validation?

Yes, you can use this for automated spec workflow validation because it integrates with the .specify workflow to automatically validate prerequisite conditions before generating clarification questions.