speckit-clarify

Identify and resolve underspecified areas in feature specification files.

Updated Jun 5, 2026

Search Tags:#automation #documentation #specification #requirements #clarification #software-engineering

Ready to run

npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-clarify-estaciolima

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/estaciolima/idle-improvement-game/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-clarify-estaciolima

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves hidden ambiguities and missing requirements in feature specifications by systematically identifying gaps and prompting for necessary decisions before development begins.

Core Features & Use Cases

Structured Ambiguity Scan: Evaluates specs against a comprehensive taxonomy covering functional, domain, UX, and non-functional requirements.
Interactive Clarification: Engages the user with a prioritized, limited-scope questioning loop to ensure high-impact decisions are captured.
Automated Integration: Automatically updates the feature specification file with clarified answers and re-validates project checklists to ensure alignment.

Quick Start

Run the speckit-clarify skill to identify and resolve missing requirements in your current feature specification file.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema

How do I eliminate ambiguity in software feature specifications before development?▼

To eliminate ambiguity in feature specifications, you can run a taxonomy-based analysis that identifies gaps across functional, domain, UX, and non-functional requirements. It interactively prompts you for high-impact decisions to ensure requirements are fully captured before implementation.

What is the best way to find missing requirements in my feature documentation?▼

Finding missing requirements in feature documentation is best handled by scanning your specs against a comprehensive taxonomy. This structured ambiguity scan highlights underspecified areas and prompts a limited-scope questioning loop to resolve them.

Do I need a specific directory structure to clarify feature specifications?▼

Yes, clarifying feature specifications requires a project structure containing a .specify directory and a valid feature specification file. The skill scans this specific file structure to identify gaps and automatically update the document with clarified answers.

How does automated clarification integrate answers back into the feature specification file?▼

Automated clarification integrates answers by automatically updating the feature specification file with your resolved decisions. It also re-validates project checklists after the interactive questioning loop to ensure total alignment across your software development workflow.

When should I use a structured taxonomy analysis for software requirements?▼

You should use a structured taxonomy analysis for software requirements when you need high-fidelity requirements before implementation planning. It is specifically designed for software development workflows where hidden ambiguities and missing requirements could derail development.