speckit.clarify

Generate up to five clarifying questions for feature specifications and update the spec file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Generate up to five precise clarification questions to surface gaps in functional requirements, data models, UX flow, and non-functional criteria.
  • Update the specification with clear, testable clarifications and create a dedicated Clarifications section (Session-based) for traceability.
  • Facilitate safer, faster alignment between product goals and engineering implementation by enforcing a structured clarification workflow.

Quick Start

Ask up to five targeted clarification questions to resolve underspecified areas in the feature spec and encode the 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 identify gaps in a feature specification before implementation?

To identify gaps in a feature specification, generate concise clarifying questions targeting functional, data, UX, and non-functional areas. This surfaces underspecified requirements and resolves them by encoding testable answers directly back into the spec.

What is the best way to update a spec file with clarifications?

Updating a spec file with clarifications involves generating targeted questions, then writing verifiable answers into a dedicated Clarifications section. This enforces safe, repeatable integration and maintains session-based traceability for alignment.

Does spec-kit require a specific project structure to clarify requirements?

Spec-kit requires a project structure containing a .specify/ directory to analyze requirements and generate targeted clarification questions. Without this directory, the structured plan and spec file updates cannot be applied.

Can I generate more than five clarification questions for a complex feature spec?

Generating clarification questions for a feature spec is limited to five high-signal prompts. This constraint enforces focus on the most critical underspecified areas across functional, data, UX, and non-functional dimensions.

Why does my specification clarification workflow need a dedicated section?

A specification clarification workflow needs a dedicated Clarifications section to ensure session-based traceability. It encodes clear, testable answers directly into the spec, facilitating safer and faster alignment between product goals and engineering implementation.