speckit-clarify

Identify and resolve underspecified areas in feature documentation through taxonomy-based analysis.

2|1|Updated Jul 28, 2026

Search Tags:#automation #workflow #specification #requirements #analysis #clarification

Ready to run

npx skills add https://github.com/0xbillw/dotfiles --skill speckit-clarify-0xbillw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/0xbillw/dotfiles/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/0xbillw/dotfiles --skill speckit-clarify-0xbillw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves ambiguity and missing decision points in feature specifications by systematically identifying gaps and recording clarifications directly into the document.

Core Features & Use Cases

Structured Ambiguity Scan: Evaluates specs against a comprehensive taxonomy covering functional, technical, and non-functional requirements.
Interactive Clarification: Engages the user with up to 5 high-impact, prioritized questions to ensure alignment before planning begins.
Automated Integration: Automatically updates the feature specification file with resolved answers and maintains a session-based audit trail.

Quick Start

Invoke the speckit-clarify skill to scan the current feature specification for ambiguities and begin the interactive clarification process.

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

To resolve ambiguity in a feature specification, you can scan the document against a structured taxonomy covering functional, technical, and non-functional requirements to identify gaps and clarify decision points.

What is taxonomy-based analysis for software requirements clarification?▼

Taxonomy-based requirements clarification is a process that evaluates feature docs against comprehensive categories to systematically identify missing decision points and record clarifications directly into the file.

How do I automate spec updates after clarifying requirements?▼

You can automate spec updates by using a clarification workflow that automatically writes resolved answers directly into the feature specification file while maintaining a session-based audit trail.

Does this clarification process support integration with project-specific extension hooks?▼

Yes, the specification clarification process satisfies integration requirements for automated spec updates, checklist validation, and workflows utilizing project-specific extension hooks.

How many questions are asked during interactive specification clarification?▼

During interactive specification clarification, you are presented with up to five high-impact, prioritized questions to ensure alignment before task planning and implementation begins.

What is the best way to refine underspecified areas before task planning?▼

The best way to refine underspecified areas before task planning is to apply a structured ambiguity scan that targets missing decision points and records clarifications interactively into the document.