skills.rest
AstralDeep
AstralDeepOFFICIAL
Explore all skills by this author →
GitHub

speckit-clarify

Identify underspecified areas in feature specifications and encode clarifications into the spec file.

Updated Aug 23, 2026
Search Tags:#workflow#specification#requirements#ambiguity#interactive#speckit#clarify
One-click install
npx skills add https://github.com/AstralDeep/astralprojection-flutter --skill speckit-clarify-astraldeep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/AstralDeep/astralprojection-flutter/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/AstralDeep/astralprojection-flutter --skill speckit-clarify-astraldeep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in a feature specification and encode clarifications back into the spec to reduce downstream rework and ensure precise implementation.

Core Features & Use Cases

  • Structured ambiguity taxonomy scan to surface gaps and uncertainties.
  • Interactive, session-based questioning that limits questions to a maximum of five.
  • Atomic, validated updates to the spec file under a dedicated Clarifications section.
  • Automatic logging of decisions and traces to support traceability and audits.

Quick Start

Initiate the speckit-clarify workflow against your current feature spec to start the interactive clarification loop.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify ambiguity in a feature specification?▼

To identify ambiguity in a feature specification, you scan for underspecified areas using a structured taxonomy. This surfaces gaps and uncertainties to ensure precise implementation and reduce downstream engineering rework.

What is the best way to clarify requirements in a spec file?▼

The best way to clarify requirements in a spec file is through an interactive questioning loop that encodes atomic, validated updates directly into a dedicated Clarifications section.

Can I limit the number of clarification questions asked during a spec review?▼

Yes, you can limit spec review questions by using an interactive, session-based questioning loop that restricts inquiries to a maximum of five, ensuring focused and efficient clarification sessions.

How do I track specification decisions for traceability and audits?▼

You track specification decisions by automatic logging of decisions and traces. This supports traceability and audits by recording atomic, validated updates made during the interactive clarification process.

When do I need an ambiguity taxonomy scan for feature spec work?▼

You need an ambiguity taxonomy scan for feature spec work when product and engineering teams must surface uncertainties before implementation. It identifies underspecified areas to prevent downstream rework and ensure precise builds.

Related Skills

Explore More Software Engineering Skills→
GenerativeAgentsGenerativeAgents

prd-writing

Generate a review-ready PRD from initial-requirements.md using the PRD template.

Official
Advanced
ev3rlitev3rlit

speckit-clarify

Resolve ambiguities in feature specs through structured clarification workflows.

Community
Advanced
luisloboluislobo

workmesh-mcp

Orchestrate WorkMesh project and task management via MCP tools.

Community
Advanced
GarethJBGarethJB

speckit-clarify

Identify underspecified areas in feature specs and encode clarifications into the document.

Community
Advanced