Where are the results of the clarification phase saved?

Answers are integrated directly into your spec.md file, and a detailed historical record of all questions, answers, and deferred assumptions is saved in a clarifications.md file.

How does the skill avoid asking too many questions?

It uses a prioritization matrix to filter questions. Only 'Critical' and 'High' priority issues result in user questions (limited to 3), while 'Medium' and 'Low' issues are documented as informed assumptions.

Can I override the assumptions made by the skill?

Yes. All deferred assumptions are documented in the spec.md and clarifications.md files with clear instructions on how to override them if the default choice doesn't meet your needs.

What is the primary purpose of the Clarification Phase skill?

It identifies and resolves critical ambiguities in your project specifications to ensure requirements are concrete and unambiguous before the implementation phase begins.

Spec Clarification Phase

Name: Spec Clarification Phase
Author: marcusgoll

bymarcusgoll

•

Productivity & Workflow

Resolves software specification ambiguities through structured questioning and priority-based filtering to solidify project scope.

The Clarification Phase skill is a core component of the Spec-Flow workflow designed to eliminate ambiguity before implementation begins. It automatically scans project specifications for clarification markers, applies a prioritization matrix to filter out minor details, and uses structured interaction tools to resolve critical scope, security, and UX decisions. By limiting user interruptions to high-impact questions and documenting lower-priority items as informed assumptions, it ensures a concrete, auditable foundation for the planning and development phases.

Key Features

01Structured user interaction using the AskUserQuestion tool

02Automated extraction of [NEEDS CLARIFICATION] markers from spec files

03Automatic integration of resolved answers back into specifications

04Generation of auditable clarification records and assumption logs

0518 GitHub stars

06Priority-based question filtering to prevent analysis paralysis

Use Cases

01Standardizing user feedback loops during spec-driven development

02Disambiguating complex feature requirements before starting the planning phase

03Reducing developer cognitive load by automating requirement prioritization

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add marcusgoll/spec-flow clarification-phase

For use in Claude.ai and ChatGPT

Download Skill