speckit-clarify

Resolve feature specification ambiguities through guided questions and recorded clarifications.

4|11|Updated Dec 14, 2025

Search Tags:#interactive #governance #traceability #feature-spec #clarifications #spec-workflow

Ready to run

npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-clarify-obsidian-owl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Obsidian-Owl/floe/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/Obsidian-Owl/floe --skill speckit-clarify-obsidian-owl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps product teams identify and resolve ambiguities in active feature specifications by guiding a structured Q&A workflow and recording decisions directly in the spec.

Core Features & Use Cases

Interactive taxonomy-driven clarification: assesses functional scope, data models, UX flows, non-functional attributes, and more.
Incremental spec updates: appends clarifications after each decision and validates completeness.
Governance and traceability: preserves a clear decision log for future audits and implementation planning.

Quick Start

Run the clarifications workflow on your current feature spec to begin capturing targeted questions and decisions.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema

How do I identify and resolve ambiguities in a feature specification?▼

To resolve ambiguities in a feature specification, use a taxonomy-driven Q&A workflow that surfaces gaps in functional scope and data models, prioritizes up to five targeted questions, and records accepted answers directly into the spec.

What is the best way to maintain traceability for feature spec clarifications?▼

Maintaining traceability for feature spec clarifications requires appending decisions directly into the specification as a clear decision log, preserving the updates for future audits and implementation planning while validating spec completeness after each change.

How do I guide targeted clarifying questions for product spec gaps?▼

Guide targeted clarifying questions for product spec gaps by using an interactive taxonomy that assesses functional scope, data models, UX flows, and non-functional attributes, prioritizing the most critical questions to surface missing requirements.

Can I validate testability and governance after updating a feature spec?▼

Yes, you can validate testability and governance after updating a feature spec by enforcing a workflow that validates the specification's completeness immediately after each clarification is appended, ensuring all decisions meet governance standards.

Does interactive spec workflow support incremental updates for active feature specifications?▼

Interactive spec workflow supports incremental updates for active feature specifications by appending clarifications sequentially after each decision and validating the spec, ensuring the document evolves safely without losing prior context.