gap-analysis

Name: gap-analysis
Availability: InStock
Author: Cole

Identify and categorize missing requirements in proposals and specifications.

Updated Oct 8, 2025

Search Tags:#requirements #specifications #edge-cases #risk-assessment #gap-analysis #ux-analysis #proposal-review

Ready to run

npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill gap-analysis-ichabodcole

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gap-analysis
Source: https://github.com/ichabodcole/project-docs-scaffold-template/tree/main/plugins/project-docs/skills/gap-analysis
Command: npx skills add https://github.com/ichabodcole/project-docs-scaffold-template --skill gap-analysis-ichabodcole

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify what's missing from proposals, specifications, or feature ideas—the unspecified flows, missing UI elements, unstated assumptions, and edge cases that must be addressed before implementation.

Core Features & Use Cases

Framework-backed review of proposals to ensure completeness and readiness for development.
Ability to map covered content, identify gaps by category (UX/Interaction, Technical, Edge Cases, Scope Boundaries), and generate actionable questions.
Reusable process for ensuring clear scope and requirements before committing to build.

Quick Start

Apply the Gap Analysis framework to a draft proposal to surface missing requirements and unanswered questions.

Frequently Asked Questions about gap-analysis

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

FAQPage Schema

How do I identify missing requirements in a project proposal?▼

Missing requirements in a project proposal are identified by applying a structured gap analysis workflow that categorizes gaps across UX, technical dependencies, edge cases, and scope boundaries to generate actionable questions for prioritization.

What is gap analysis in product management and UX design?▼

Gap analysis in product management is a reproducible framework that detects unspecified flows, unstated assumptions, and missing UI elements within feature specifications to ensure proposal completeness before development begins.

How do I find edge cases and scope boundaries in feature specifications?▼

Edge cases and scope boundaries in feature specifications are found by mapping existing content against a structured framework, isolating technical dependencies, and generating targeted questions to clarify scope limits.

Does this gap analysis framework work for reviewing technical dependencies?▼

Yes, the gap analysis framework explicitly reviews technical dependencies by mapping covered proposal content and generating actionable questions to address unstated assumptions and technical gaps within specifications.

What is the best way to prioritize gaps found in a draft proposal?▼

The best way to prioritize gaps found in a draft proposal is to document them using a structured gap list categorized by UX, technical, edge case, and scope boundaries, which prepares teams for direct prioritization and implementation.

When should I perform a gap analysis on my specifications?▼

You should perform a gap analysis on your specifications before committing to build, ensuring clear scope and resolving missing UI elements, unstated assumptions, and edge cases early in the proposal review stage.