clarify-requirements

Name: clarify-requirements
Availability: InStock
Author: gjalla

Identify hidden gaps and unstated assumptions in requirement specifications.

1|Updated Mar 8, 2026

Search Tags:#architecture #specification #requirements #analysis #clarification #gap-identification

Ready to run

npx skills add https://github.com/gjalla/gjalla-plugin --skill clarify-requirements

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clarify-requirements
Source: https://github.com/gjalla/gjalla-plugin/tree/main/claude/skills/clarify-requirements
Command: npx skills add https://github.com/gjalla/gjalla-plugin --skill clarify-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often start implementation with incomplete or ambiguous specifications, leading to costly rework. This Skill systematically uncovers hidden gaps, unstated assumptions, and edge cases in requirements before any code is written.

Core Features & Use Cases

Negative Space Analysis: Identifies what the spec does not say but should, across failure modes, boundaries, state transitions, timing, permissions, compatibility, and observability.
Contextual Enrichment: Optionally queries gjalla for existing capabilities, data flows, and architectural rules to ground questions in current system context.
Structured Clarification Output: Generates a prioritized list of critical, important, and minor questions plus assumptions, ready to share with stakeholders.

Quick Start

Request the skill to clarify the requirements for the provided feature description.

Frequently Asked Questions about clarify-requirements

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

FAQPage Schema

How do I identify hidden gaps and ambiguities in a software requirement specification?▼

You clarify feature requests by applying negative space analysis to identify what the spec does not say but should, covering failure modes, boundaries, state transitions, and permissions to generate a prioritized clarification document for stakeholders.

What is negative space analysis in requirements clarification?▼

Negative space analysis in requirements clarification targets what the spec omits but should include, systematically probing failure modes, boundaries, state transitions, timing, permissions, compatibility, and observability to expose unstated assumptions.

Can I use requirement clarification on user stories and task descriptions?▼

Yes, requirement clarification applies directly to feature requests, user stories, and task descriptions, systematically surfacing critical questions and unstated assumptions to prevent costly rework during implementation.

How do I generate a structured clarification document for stakeholders?▼

Generate a clarification document by grounding questions in current system context such as existing capabilities and data flows, producing a prioritized list of critical, important, and minor questions plus assumptions ready to share with stakeholders.

Why do I need to clarify requirements before coding?▼

Clarifying requirements before coding prevents costly rework by systematically uncovering hidden gaps, unstated assumptions, and edge cases in specifications that lead to implementation errors when teams start with incomplete or ambiguous documentation.