speckit-clarify

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

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/TKlerx/webapp-template --skill speckit-clarify-tklerx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/TKlerx/webapp-template/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/TKlerx/webapp-template --skill speckit-clarify-tklerx

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies underspecified areas in feature specifications by asking up to 5 highly targeted clarification questions, reducing ambiguity and improving the spec.

Core Features & Use Cases

  • Targeted Clarification: Asks up to 5 questions to resolve ambiguity in feature specs.
  • Spec Integration: Encodes answers back into the spec file.
  • Compatibility: Requires spec-kit project structure with .specify/ directory.
  • Use Case: Use this Skill to clarify a new feature spec for your project, ensuring all requirements are clear and actionable.

Quick Start

Run /speckit-clarify to begin clarifying your feature spec.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify underspecified areas in a feature specification?

Targeted clarification questions identify underspecified areas in a feature specification by posing up to 5 highly targeted queries to resolve ambiguity and improve the spec.

Do I need a spec-kit project structure to clarify feature specs?

Yes, you need a spec-kit project structure with a .specify/ directory to clarify feature specs. This environment is required to encode answers back into the spec file successfully.

How do I refine a feature specification by asking clarification questions?

You refine a feature specification by running a clarification process that asks up to 5 targeted questions. Answers are then encoded directly back into the spec file to ensure requirements are clear and actionable.

What is the best way to reduce ambiguity in project requirements definition?

The best way to reduce ambiguity in project requirements definition is to apply targeted specification refinement. This method poses highly specific questions to resolve underspecified areas within your feature specs.

Are there limitations when using specification refinement for feature engineering?

A limitation of specification refinement for feature engineering is that it requires an existing spec-kit project structure. Additionally, the clarification process is constrained to asking a maximum of 5 targeted questions per spec.