skills.rest
EONMUN
EONMUNOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec_driven_development.clarify

Clarify vague specifications by eliciting structured questions and recording answers.

1|Updated Jun 30, 2025
Search Tags:#planning#specification#clarification#edge-cases#acceptance-criteria#structured-questions
One-click install
npx skills add https://github.com/EONMUN/EONMUN --skill spec-driven-development-clarify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec_driven_development.clarify
Source: https://github.com/EONMUN/EONMUN/tree/main/.claude/skills/spec_driven_development.clarify
Command: npx skills add https://github.com/EONMUN/EONMUN --skill spec-driven-development-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves ambiguities in specifications by guiding a structured questioning process to ensure complete and testable docs before implementation.

Core Features & Use Cases

  • Structured clarification workflow to identify ambiguities in user stories, acceptance criteria, edge cases, data flows, and non-functional requirements.
  • Question-driven refinement that generates targeted, one-topic-per-question prompts to collect precise answers.
  • Spec updates and validation that document clarifications, update acceptance criteria, and prepare the spec for technical planning.

Quick Start

Launch a clarification session against specs/[feature-name]/spec.md, identify ambiguities, and generate structured questions. Record answers in a Clarifications section and update the spec accordingly.

Frequently Asked Questions about spec_driven_development.clarify

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

FAQPage Schema
How do I clarify vague specifications before starting technical planning?▼

Clarifying vague specifications involves a structured workflow that identifies ambiguities in user stories, acceptance criteria, edge cases, and data flows to produce a testable spec document ready for technical planning.

What is the best way to identify edge cases and refine acceptance criteria in a spec?▼

Refining acceptance criteria and identifying edge cases is achieved through question-driven refinement that generates targeted, one-topic-per-question prompts to collect precise answers and resolve specification ambiguities.

How do I document specification clarifications for a specific feature?▼

Documenting specification clarifications involves recording answers in a dedicated Clarifications section within your feature's spec file, which simultaneously updates acceptance criteria and validation checks.

Does structured specification clarification require an existing spec document?▼

Structured specification clarification requires an existing specification document located at specs/[feature-name]/spec.md to serve as the baseline for identifying ambiguities and applying updates.

When should I use a structured questioning workflow for software specifications?▼

A structured questioning workflow for software specifications is needed when resolving ambiguities in non-functional requirements and data flows, ensuring documentation is complete and testable before implementation begins.

Related Skills

Explore More Software Engineering Skills→
SalmanO7SalmanO7

specification-writing-skill

Create feature specifications with user stories, FRs, scenarios, and acceptance criteria.

Community
Advanced
AcidicSoilAcidicSoil
1

refine-story

Refine rough user stories into sprint-ready documentation with acceptance criteria and technical guidance.

Community
Advanced
mattwoodcomattwoodco
3

spec-export

Export structured specification documents into Linear and GitHub Issues tickets.

Community
Advanced
Tubular-HealthTubular-Health
1

define

Create precise issue specifications for Linear or Jira through structured Socratic questioning.

Official
Advanced