speckit-clarify

Identifies gaps in feature specs by asking up to 5 targeted questions.

3|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/opencue/colony --skill speckit-clarify-opencue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/opencue/colony/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/opencue/colony --skill speckit-clarify-opencue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify underspecified areas in feature specifications by asking up to 5 highly targeted clarification questions.

Core Features & Use Cases

  • Targeted Clarification: Asks up to 5 questions to reduce ambiguity in feature specifications.
  • Spec-Kit Integration: Requires spec-kit project structure with a .specify/ directory.
  • Use Case: Use this Skill to ensure your feature specifications are clear and complete before proceeding with planning or implementation.

Quick Start

Run /speckit-clarify to start the clarification process for your spec.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I clarify feature specifications before implementation?

This skill clarifies feature specifications by asking up to 5 targeted questions to identify underspecified areas. It requires a spec-kit project structure with a .specify/ directory and user interaction to answer the questions.

What is specification clarification and when do I need it?

Specification clarification is the process of resolving ambiguity in feature specifications by asking targeted questions. You need it when your feature specifications are underspecified and you want to ensure clarity before proceeding with planning or implementation.

How do I identify underspecified areas in my feature engineering project?

You identify underspecified areas by running a clarification process that asks up to 5 targeted questions. This interactive process helps reduce ambiguity and ensures your feature specifications are complete.

Do I need a spec-kit project structure to use this clarification process?

Yes, you need a spec-kit project structure with a .specify/ directory to use this clarification process. The tool is designed to integrate with project hooks within this specific environment.

What is the best way to reduce ambiguity in feature specifications?

The best way to reduce ambiguity is to ask up to 5 targeted clarification questions. This approach pinpoints underspecified areas in your feature specifications, ensuring clarity before you move forward with implementation.

What are the limitations of automated specification clarification?

The main limitation is that it requires user interaction to answer the generated questions and cannot resolve ambiguities automatically. Additionally, it is limited to asking up to 5 questions per feature specification.