speckit-clarify

Identify underspecified areas in feature specifications and encode clarifications into structured updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Surface gaps and ambiguities in feature specs using a structured clarification workflow.
  • Generate up to 5 targeted questions and map each answer back into the spec as concrete updates.
  • Maintain a persistent Clarifications section with per-session logging and atomic updates after each accepted answer.

Quick Start

Clarify the current feature spec to resolve ambiguities.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify ambiguities in a feature specification?▼

Spec clarification works by analyzing your feature spec for underspecified areas, generating up to 5 targeted questions about requirements and constraints, then mapping your answers back into the spec as structured updates within a persistent Clarifications section.

How do I resolve underspecified requirements in a feature spec?▼

You resolve underspecified requirements by generating up to 5 targeted clarification questions about scope and data models, then encoding the accepted answers directly back into the feature spec as atomic, structured updates with per-session logging.

What is the best way to log clarifications for a feature spec?▼

The best way to log clarifications is maintaining a persistent Clarifications section within the feature spec that records per-session logs and applies atomic updates after each accepted answer to ensure traceability of requirement changes.

Can I generate targeted questions to cover non-functional constraints in my spec?▼

Yes, you can generate targeted questions to cover non-functional constraints. The clarification workflow analyzes your feature spec and surfaces gaps across requirements, scope, UX flow, data models, and non-functional constraints simultaneously.

Does spec clarification work without external dependencies?▼

Yes, spec clarification works without external dependencies. The workflow operates independently to analyze feature specifications, identify underspecified areas, and encode structured updates directly into the spec using a self-contained clarification process.