speckit-clarify

Scan feature specs for gaps and record clarifications before planning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature specification by prompting up to five focused clarifications and recording answers back into the spec to reduce ambiguity and rework.

Core Features & Use Cases

  • Interactive ambiguity discovery: runs a structured checklist across functional goals, data models, UX flows, and non-functional criteria to surface gaps.
  • Guided documentation: records clarifications directly in the spec under a dedicated Clarifications section.
  • Safe planning handoff: supports a minimized risk path before planning or invoking /speckit.plan.

Quick Start

Run the speckit-clarify workflow on the active spec to begin the clarification session.

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 and resolve ambiguity in a feature specification?

To resolve ambiguity in a feature specification, you can run a structured scan across functional scope, data models, UX flows, and non-functional attributes to surface underspecified gaps through targeted questions.

What is the best way to document clarifications directly into a feature spec?

Documenting clarifications involves recording the answers from targeted questions directly back into the specification under a dedicated section, ensuring the updated spec reduces rework before planning begins.

How do I prepare a feature specification for planning by reducing underspecified requirements?

Preparing a specification for planning requires running an interactive checklist that prompts up to five focused clarifications on high-impact categories, validating inputs against the existing spec to minimize risk.

Does the ambiguity clarification process restrict questions to specific categories?

Yes, the ambiguity clarification process restricts questions to high-impact categories including functional scope, data model, UX flow, and non-functional attributes to efficiently target underspecified spec areas.

Can I execute user-provided code while scanning a feature spec for ambiguity?

No, scanning a feature spec for ambiguity avoids executing user-provided code entirely, ensuring safety by validating inputs strictly against the existing specification without running external scripts.