speckit-clarify

Name: speckit-clarify
Availability: InStock
Author: Maru

Prompt targeted clarifying questions and encode answers into feature specifications.

Updated Apr 2, 2026

Search Tags:#planning #requirements #clarification #ambiguity #spec #speckit

Ready to run

npx skills add https://github.com/Maru1301/Yeet --skill speckit-clarify-maru1301

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/Maru1301/Yeet/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/Maru1301/Yeet --skill speckit-clarify-maru1301

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

speckit-clarify identifies underspecified areas in the current feature specification by prompting up to five focused questions and encoding the answers back into the spec.

Core Features & Use Cases

Structured ambiguity scanning across functional scope, data model, UX flows, non-functional requirements, and integrations.
Interactive one-question-at-a-time loop that surfaces high-impact uncertainties and records decisions in the spec.
Automated integration into the spec under a Clarifications section (Session YYYY-MM-DD) with traceable decisions and testable outcomes.
Validates completeness with a lightweight checklist to reduce downstream rework and re-specification.

Quick Start

Start a clarifications session against your active feature spec to surface and resolve ambiguities before planning.

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

You can resolve feature specification ambiguity by prompting up to five targeted clarifying questions one at a time. This interactive loop prioritizes high-impact underspecified areas and encodes your answers directly back into the spec.

How do I update a spec with clarifications and traceable decisions?▼

You update a spec with clarifications by encoding answers into an automated Clarifications section tagged with the session date. This records traceable decisions and testable outcomes directly within the existing project structure.

Can I use this clarification workflow with an existing spec-kit project structure?▼

Yes, you can use this clarification workflow with an existing spec-kit project structure. It operates within the .specify directory to ensure full compatibility with your current planning workflows.

What is the best way to reduce downstream rework when defining feature requirements?▼

The best way to reduce downstream rework when defining feature requirements is to validate completeness with a lightweight checklist after resolving ambiguities. This prevents costly re-specification by catching missing details early.

How many clarifying questions does this specification tool prompt during a session?▼

This specification tool prompts up to five focused clarifying questions during a session. It asks a single question at a time to systematically address non-functional requirements, integrations, and scope ambiguities.