speckit-clarify

Resolve ambiguities in feature specs through structured clarification workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit Clarify provides a structured, repeatable workflow to resolve underspecified requirements by guiding coverage-based questioning and recording answers directly in the spec clarifications section.

Core Features & Use Cases

  • Structured ambiguity scans across functional scope, data model, UX flow, and non-functional attributes.
  • In-context session logging that updates the spec with a dedicated Clarifications section and a session subheading for traceability.
  • Automatic generation of a prioritized queue of follow-up questions to minimize downstream rework and align with planning.

Quick Start

Review the active spec and start a one-session clarification cycle to resolve ambiguities.

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 a feature specification before planning?▼

You can resolve ambiguities in a feature specification by running a structured clarification workflow that scans functional scope, data model, and UX flows to identify gaps and generate prioritized follow-up questions.

How does a structured clarification workflow handle requirement traceability?▼

A structured clarification workflow ensures requirement traceability by persisting accepted answers directly into a dedicated Clarifications section and session subheading within the spec file after each response.

What is the best way to cut rework caused by underspecified requirements?▼

The best way to cut rework from underspecified requirements is to perform a systematic ambiguity scan across non-functional attributes and functional scope, generating a prioritized queue of coverage-based questions to validate the spec state.

Does this clarification workflow require any external dependencies or components?▼

No, this clarification workflow operates without any external dependencies or components, allowing you to directly resolve underspecified requirements and update the spec file in a self-contained session cycle.

How do I generate a coverage report for next steps after clarifying a spec?▼

You generate a coverage report for next steps by completing a one-session clarification cycle, which validates the plan-ready spec state and outputs a concise summary of resolved ambiguities and remaining follow-up actions.