Can it help with technical architecture decisions?

No, it intentionally avoids technical implementation details like database choices or API protocols to focus exclusively on user outcomes and business logic.

What documentation format does it work best with?

It is optimized for spec.md files commonly used in the Human-in-Loop framework but can analyze any requirement-heavy documentation or project descriptions.

How does it handle edge cases?

The skill systematically checks each user story and flow to identify missing error states, permission gaps, and boundary conditions from a user perspective.

Why does it provide multiple choice options for questions?

Providing concrete options allows stakeholders to make decisions quickly, reduces ambiguity, and prevents the back-and-forth common with open-ended questions.

How does this differ from standard code reviews?

While code reviews focus on implementation and syntax, this skill focuses on the 'what' and 'why' of product requirements to ensure the right features are being built.

Spec Gap Analyzer

Name: Spec Gap Analyzer
Author: deepeshBodh

bydeepeshBodh

•

コラボレーションツール

Identifies missing requirements and ambiguities in project specifications by generating product-focused clarifying questions for stakeholders.

概要

The Spec Gap Analyzer skill transforms Claude into a proactive product analyst that reviews specification documents to find critical gaps before implementation begins. By focusing strictly on product-level decisions rather than technical implementation details, it helps bridge the communication gap between developers and stakeholders. The skill automatically classifies issues by severity—Critical, Important, or Minor—and frames every finding as a clear decision with concrete options, ensuring that requirements are airtight and reducing costly rework during the development phase.

主な機能

Automated identification of missing user expectations and business rules
Decision-based framing with multiple-choice options for stakeholders
Product-focused questioning that avoids implementation-heavy jargon
7 GitHub stars
Severity-based classification to prioritize critical project blockers
Comprehensive quality checklist covering user stories and success criteria

ユースケース

Reviewing a new spec.md file to find ambiguities before writing code
Generating a structured list of questions for a product owner after receiving a brief
Identifying missing edge cases in business logic for complex feature requirements

概要

主な機能

Automated identification of missing user expectations and business rules
Decision-based framing with multiple-choice options for stakeholders
Product-focused questioning that avoids implementation-heavy jargon
7 GitHub stars
Severity-based classification to prioritize critical project blockers
Comprehensive quality checklist covering user stories and success criteria

ユースケース

Reviewing a new spec.md file to find ambiguities before writing code
Generating a structured list of questions for a product owner after receiving a brief
Identifying missing edge cases in business logic for complex feature requirements