speckit-clarify

Identify and resolve ambiguities in feature specifications through structured questioning.

25|1|Updated Nov 10, 2023

Search Tags:#workflow #documentation #specification #requirements #clarification #ambiguity

Ready to run

npx skills add https://github.com/shaman007/home-k3s --skill speckit-clarify-shaman007

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the common issue of vague or incomplete feature specifications by systematically identifying missing information and guiding the user to provide necessary details.

Core Features & Use Cases

Ambiguity Detection: Scans feature specifications against a comprehensive taxonomy to find gaps in functional, technical, and UX requirements.
Structured Clarification: Engages the user with targeted, high-impact questions to resolve uncertainties before development begins.
Automated Integration: Automatically updates the specification file with the clarified answers, ensuring the documentation remains the single source of truth.

Quick Start

Invoke the speckit-clarify skill to analyze the current feature specification and begin the guided 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 resolve ambiguities in feature specifications before development?▼

To resolve ambiguities in feature specifications, you can use a structured questioning workflow that scans for functional, technical, and UX gaps, then updates the specification file directly with clarified requirements to ensure alignment.

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

Identifying missing requirements involves scanning the feature specification against a comprehensive taxonomy to detect functional, technical, and UX gaps, reducing downstream development risk through targeted clarification questions.

How do I automate feature specification clarification and updates?▼

Automating feature specification clarification uses a guided workflow that engages you with high-impact questions and automatically integrates your answers directly into the specification file, maintaining it as a single source of truth.

When do I need a structured clarification process for documentation?▼

You need a structured clarification process for documentation when your feature specifications are vague or incomplete, posing downstream development risks due to missing functional, technical, or UX details.

Does specification clarification work without external dependencies?▼

Yes, specification clarification works without external dependencies by running internal scripts to analyze feature specs, identify ambiguities, and update the documentation directly without requiring additional packages.