skills.rest
gmliao
gmliaoCOMMUNITY
Explore all skills by this author →
GitHub

clarify

Clarify underspecified areas in functional specifications through structured questioning.

1|Updated Nov 22, 2025
Search Tags:#planning#documentation#specification#requirements#questioning#stakeholders#clarify
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill clarify-gmliao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/SpecKit/clarify
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill clarify-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify and clarify underspecified areas in functional specifications before moving to technical planning.

Core Features & Use Cases

  • Structured, sequential clarification to resolve gaps.
  • Coverage-based questioning across Data Model, User Interactions, Business Rules, Performance & Scale, Integration Points.
  • Record clarifications and update specifications to ensure readiness for planning.

Quick Start

Use /speckit.clarify to identify specification gaps and record clarifications.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I clarify gaps in a functional specification before planning?▼

Clarify specification gaps by using a structured, sequential questioning process across data models, user interactions, and business rules to resolve ambiguities and improve planning accuracy. This ensures functional specifications are fully defined before technical design begins.

What areas should I review to resolve ambiguities in requirements documentation?▼

Review requirements documentation across five core areas: data models, user interactions, business rules, performance and scale, and integration points. Questioning these dimensions systematically identifies missing details and inconsistencies to ensure specification readiness.

When do I need to clarify underspecified areas in a specification?▼

Clarify underspecified areas during specification reviews before moving to technical planning, design, or requirements refinement. This step is necessary when functional specifications contain ambiguities, missing details, or inconsistencies that could impact downstream development accuracy.

How do I record clarifications back into a specification?▼

Record clarifications back into the specification by capturing stakeholder answers gathered through the structured questioning process. This updates the functional specification to reflect resolved gaps, ensuring the documentation remains accurate for subsequent planning phases.

Can I use structured questioning to address missing details for integration points?▼

Structured questioning explicitly covers integration points alongside data models, user interactions, business rules, and performance. Applying this sequential process identifies and resolves missing details within integration specifications before technical planning begins.

Related Skills

Explore More Product & Management Skills→
Omar-ObandoOmar-Obando
44

requirements-engineering

Convert stakeholder needs into testable requirements with traceability matrices.

Community
Intermediate
htlin222htlin222
77

sc-design

Designs system architecture, APIs, component interfaces, and technical specifications for software development.

Community
Intermediate
sobhanashinesobhanashine
1

plan-design-review

Review design plans with ratings and improvement suggestions per dimension.

Community
Intermediate
roderikroderik
2

ask-questions-if-underspecified

Clarify underspecified requests with 1-5 must-have questions before implementation.

Community
Basic