skills.rest
pradeepmouli
pradeepmouliCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Clarify underspecified feature requirements through an interactive five-question loop.

2|Updated Jan 29, 2026
Search Tags:#workflow#planning#requirements#ambiguity#spec-kit#clarify#spec-management
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-clarify-pradeepmouli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-clarify
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-clarify-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguities in requirements derail planning and increase risk; this skill provides a repeatable workflow to surface, document, and resolve gaps before implementation.

Core Features & Use Cases

  • Structured ambiguity detection and coverage analysis across functional, data, UX, non-functional, and edge-case categories.
  • Interactive questioning loop with up to five questions, guiding stakeholders to clear decisions.
  • Automatic integration of accepted answers into a Clarifications section of the spec with traceable decisions.
  • Supports planning-phase risk reduction and change management.

Quick Start

Initialize a spec and start the interactive clarification loop to surface and resolve ambiguities before planning.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify ambiguous requirements before starting feature planning?▼

To clarify ambiguous requirements, you can run an interactive questioning loop that surfaces underspecified areas across functional, data, UX, and edge-case categories. This structured workflow guides stakeholders to clear decisions before implementation begins.

What is the best way to resolve underspecified product specifications?▼

The best way to resolve underspecified product specifications is through structured ambiguity detection and coverage analysis. An interactive questioning loop caps at five questions, guiding stakeholders to clear, traceable decisions that reduce planning risk.

How do I document clarified decisions directly into a spec file?▼

You document clarified decisions by applying on-disk updates to the spec file. Accepted answers from the questioning loop are automatically integrated into a Clarifications section, ensuring traceable decisions are captured within the specification.

Can I use a structured workflow to reduce planning risk for feature specifications?▼

Yes, a structured workflow can reduce planning risk by identifying gaps in feature specifications early. By capturing traceable decisions and resolving ambiguities before implementation, teams avoid derailment and manage change effectively.

Does the interactive clarification loop limit the number of questions per spec?▼

Yes, the interactive clarification loop caps at five questions per spec. This constraint ensures focused ambiguity resolution, guiding stakeholders to clear decisions without overwhelming the requirements gathering process.

Related Skills

Explore More Product & Management Skills→
datamaker-krdatamaker-kr
1

consistency-analysis

Detect inconsistencies, gaps, and conflicts across specification documents.

Official
Advanced
stribusstribus
1

speckit-clarify.agent

Identify ambiguities in feature specifications and propose clarifying questions.

Community
Advanced
zthxxxzthxxx

openspec-new-change

Initialize OpenSpec change scaffolds and monitor artifact status.

Community
Basic
CongtrinhhCongtrinhh

speckit-clarify

Scan feature specs for ambiguity and collect up to five targeted answers.

Community
Advanced