speckit-clarify

Run a structured clarification workflow that records answers into feature specifications.

Updated Aug 23, 2026

Search Tags:#automation #planning #requirements #clarification #ambiguity #interaction #spec

Ready to run

npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-clarify-leonardomoraisf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/leonardomoraisf/commonplace-pinboard-extension/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-clarify-leonardomoraisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit Clarify identifies and resolves ambiguous or underspecified requirements in the active feature specification, ensuring clarifications are recorded and traceable in the spec.

Core Features & Use Cases

Preflight prerequisites check and current spec loading to establish a reliable starting point.
Structured ambiguity scan across Functional Scope & Behavior, Domain & Data Model, Interaction & UX Flow, Non-Functional Quality Attributes, Integration & External Dependencies, Edge Cases & Failure Handling, and Terminology & Consistency.
Generate and maintain an internal, prioritized queue of clarification questions (up to 5) to guide planning and reduce downstream rework.
Apply accepted answers immediately to the spec under a dedicated Clarifications section, with session tagging and testable updates.
Provide a post-session coverage summary to inform planning decisions and next steps.

Quick Start

Run the Speckit Clarify workflow against the current spec to identify ambiguities and generate prioritized questions 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 resolve ambiguity in feature specifications before planning?▼

To resolve ambiguity in feature specifications, run a structured clarification workflow that scans functional scope, data models, and UX flows, then records accepted answers directly into the spec. This ensures all decisions are explicit, complete, and testable before planning begins.

What is the best way to identify underspecified requirements in a feature spec?▼

The best way to identify underspecified requirements is to perform a structured ambiguity scan across dimensions like non-functional quality attributes, integration dependencies, and edge cases. This process generates a prioritized queue of up to five high-impact questions to guide clarification.

How do I ensure my spec clarifications are traceable and testable?▼

To ensure spec clarifications are traceable and testable, apply accepted answers immediately to the spec under a dedicated Clarifications section with session tagging. This updates the specification after each answer to maintain explicit and complete decision records.

Can I automate the clarification process for multiple dimensions like data models and UX flows?▼

Yes, you can automate the clarification process across dimensions including Domain & Data Model, Interaction & UX Flow, and External Dependencies. The workflow iteratively asks up to five high-impact questions and updates the spec after each accepted answer to reduce downstream rework.

What prerequisites do I need before running a spec clarification workflow?▼

Before running a spec clarification workflow, you need a preflight prerequisites check and a loaded current feature specification. Establishing this reliable starting point allows the system to accurately scan for ambiguities and generate prioritized clarification questions.

When should I use a structured clarification workflow for product requirements?▼

You should use a structured clarification workflow for product requirements before planning to ensure decisions are explicit. It is applied to identify and resolve ambiguity across functional, data, UX, and non-functional dimensions, providing a post-session coverage summary to inform next steps.