speckit-clarify

Generate up to five clarification questions and update the spec's Clarifications section.

Updated May 20, 2026
One-click install
npx skills add https://github.com/igmo71/Myrmex --skill speckit-clarify-igmo71
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/igmo71/Myrmex/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/igmo71/Myrmex --skill speckit-clarify-igmo71

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Underspecified feature specifications lead to misinterpretation, delays, and rework. speckit-clarify identifies gaps by asking targeted questions and encoding answers back into the spec to align stakeholders.

Core Features & Use Cases

  • Proposes up to five focused clarification questions to resolve underspecification in a feature spec.
  • Creates and maintains a Clarifications section with a per-session history, ensuring an auditable trace of decisions.
  • Applies accepted answers directly to the spec, reducing downstream rework and scope drift.

Quick Start

Run the clarifications workflow on the current spec and commit accepted answers to the Clarifications section.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify gaps in a feature specification before development?

Feature specification clarification works by generating up to five targeted questions to expose underspecified areas. Accepted answers are then applied directly into a dedicated Clarifications section to provide an auditable trail of decisions.

How do I track clarification questions and decisions in documentation?

You can track specification decisions by recording accepted answers and session history under a dedicated Clarifications section. This maintains an auditable trail of decisions to minimize rework and misalignment across stakeholders.

What is the best way to prevent scope drift in requirements documentation?

The best way to prevent scope drift in requirements is to apply accepted clarification answers directly to the spec. Encoding these decisions creates an auditable trace that minimizes downstream rework and misalignment.

Does the clarification workflow support multiple review sessions for a single spec?

Yes, the clarification workflow supports multiple sessions by maintaining a per-session history within the Clarifications section. This records an ongoing, auditable trace of decisions as the feature specification evolves.

When should I use a structured clarification process for QA requirements?

You should use a structured clarification process for QA requirements when a feature specification is underspecified and risks misinterpretation. Generating targeted questions early minimizes downstream rework and stakeholder misalignment.