speckit-clarify

Ask up to five targeted questions and encode answers into a feature spec.

60|12|Updated Aug 1, 2013
One-click install
npx skills add https://github.com/vtex/front.phone --skill speckit-clarify-vtex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/vtex/front.phone/tree/main/.agents/skills/speckit-clarify
Command: npx skills add https://github.com/vtex/front.phone --skill speckit-clarify-vtex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit specs often start underspecified, leading to rework, misaligned acceptance criteria, and unclear implementation decisions.

Core Features & Use Cases

  • Targeted clarification: Asks up to 5 highly focused questions to resolve the biggest gaps and ambiguities.
  • Spec-first workflow: Records answers directly into the feature spec in the appropriate sections.
  • Operational guardrails: Checks prerequisites, supports extension hooks, and enforces a strict questioning flow to keep changes consistent and testable.

Quick Start

Run /speckit-clarify with your current feature spec context so the assistant asks up to five targeted questions and writes the answers back into the 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?

Clarify feature specifications by asking up to five targeted clarification questions that identify underspecified areas. The tool scans for ambiguities in functional behavior, data models, and edge cases, then encodes the answers directly back into the spec.

What is the best way to resolve ambiguities in product requirements?

Resolve ambiguities in product requirements through structured ambiguity scanning. This approach enforces a strict questioning flow to address gaps in UX flow, non-functional requirements, and terminology consistency before planning begins.

How do acceptance criteria get updated during specification clarification?

Acceptance criteria get updated through incremental spec updates after each accepted answer. As you resolve gaps in the feature spec, the tool records the answers directly into the appropriate spec sections to keep changes consistent.

Can I use extension hooks to customize the specification clarification workflow?

You can customize the specification clarification workflow using optional extension hook execution via .specify/extensions.yml. This allows you to integrate specific operational guardrails while the tool checks prerequisites and enforces its questioning flow.

What are the limitations of automated spec clarification questioning?

Automated spec clarification questioning is limited to a maximum of five targeted questions per session. This constraint ensures highly focused gap resolution but means highly complex feature specs may require multiple sequential sessions to fully clarify.