analysis-specifications

Identify specification gaps and generate clarifying product questions with severity classifications.

35|2|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/deepeshBodh/human-in-loop --skill analysis-specifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analysis-specifications
Source: https://github.com/deepeshBodh/human-in-loop/tree/main/plugins/humaninloop/skills/analysis-specifications
Command: npx skills add https://github.com/deepeshBodh/human-in-loop --skill analysis-specifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specifications often miss critical product decisions, leading to ambiguity, rework, and delays. This skill identifies gaps in specifications and generates focused clarifying questions to align stakeholders on what must be decided before implementation.

Core Features & Use Cases

  • Generates product-focused clarifying questions with concrete options, helping surface missing acceptance criteria and user-story gaps.
  • Classifies gaps by severity (Critical, Important, Minor) and outputs a structured, decision-ready report.
  • Supports spec-review workflows by prompting stakeholders to resolve ambiguities before planning and design.

Quick Start

Open spec.md and run the review workflow to surface gaps and clarifying questions.

Frequently Asked Questions about analysis-specifications

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

FAQPage Schema
How do I identify gaps in user stories and acceptance criteria before implementation?

Spec review identifies gaps in specifications and generates focused clarifying questions for stakeholders. It surfaces missing acceptance criteria and user-story gaps by classifying ambiguities by severity and providing concrete options to resolve them.

What is the best way to generate clarifying questions for stakeholders from a product spec?

Generating clarifying questions for stakeholders from a product spec involves analyzing the document for missing decisions and outputting a structured gap analysis. This report includes severity classifications and 2-3 concrete options per gap to align stakeholders on what must be decided.

How do I check if my specifications are complete enough for development planning?

Checking specification completeness involves validating user stories and acceptance criteria to surface all gaps. A structured gap analysis categorizes missing decisions by severity—Critical, Important, or Minor—ensuring stakeholders resolve ambiguities before planning and design phases.

Can I use spec review to find missing acceptance criteria in user stories?

Yes, spec review can be used to find missing acceptance criteria in user stories. The process applies acceptance criteria validation and user story completeness checks to surface all gaps, producing a decision-ready report with severity classifications and concrete options.

What are the limitations of automated gap analysis for product specifications?

Automated gap analysis for product specifications stays strictly product-focused and does not replace technical architectural reviews. It surfaces ambiguities and missing decisions in user stories but requires stakeholders to actively evaluate the generated options and rationale to finalize requirements.