skills.rest
mori-shin-x
mori-shin-xCOMMUNITY
Explore all skills by this author →
GitHub

speckit-clarify

Identify and resolve ambiguities in feature specifications through structured requirement analysis.

12|2|Updated Jun 19, 2026
Search Tags:#documentation#specification#requirements#clarification#quality-assurance#software-engineering
One-click install
npx skills add https://github.com/mori-shin-x/artgraph --skill speckit-clarify-mori-shin-x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-clarify
Source: https://github.com/mori-shin-x/artgraph/tree/main/.claude/skills/speckit-clarify
Command: npx skills add https://github.com/mori-shin-x/artgraph --skill speckit-clarify-mori-shin-x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the common issue of vague or incomplete feature specifications by systematically identifying missing decision points and recording clarifications directly into your documentation.

Core Features & Use Cases

  • Ambiguity Detection: Performs a structured scan across functional, technical, and UX domains to find gaps in requirements.
  • Interactive Clarification: Guides the user through a prioritized, high-impact questioning loop to resolve uncertainties.
  • Automated Integration: Automatically updates the feature specification file with resolved answers and re-validates quality checklists.

Quick Start

Invoke the speckit-clarify skill to scan the current feature specification and resolve any critical ambiguities through an interactive question session.

Frequently Asked Questions about speckit-clarify

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

FAQPage Schema
How do I identify ambiguities in feature specifications?▼

Ambiguities in feature specifications are identified through a structured scan across functional, technical, and UX domains to find missing decision points and gaps in requirements.

What is the best way to resolve vague requirements in software engineering?▼

Resolving vague requirements involves guiding users through a prioritized, interactive questioning loop to clarify uncertainties and ensure functional and non-functional constraints are explicitly defined.

How do I automate documentation updates for requirement clarifications?▼

Automated documentation updates record resolved answers directly into the feature specification file and automatically re-validate quality checklists to maintain high-fidelity, testable requirements.

Can I use interactive questioning to improve quality assurance for my specs?▼

Yes, interactive clarification improves quality assurance by conducting structured, multi-domain requirement analysis to ensure all critical functional and non-functional constraints are recorded.

When do I need to perform gap analysis on my project requirements?▼

Gap analysis on project requirements is needed when you must ensure high-fidelity, testable requirements by verifying that all functional, technical, and UX decision points are explicitly defined.

Related Skills

Explore More Software Engineering Skills→
roycolumbia-coderoycolumbia-code

gsd-spec-phase

Generate SPEC.md documents with ambiguity scoring for project phases.

Community
Advanced
chaimtchaimt

spec-checklist

Generate requirement quality checklists from feature specification files.

Community
Advanced
inflexa-aiinflexa-ai
29

openspec-sync-specs

Merge delta requirement changes into main OpenSpec specification files.

Official
Intermediate
silaslopes100silaslopes100

reversa-clarify

Identify and resolve ambiguities in project requirement documents through gap analysis and user questioning.

Community
Intermediate