gap-analysis

Name: gap-analysis
Availability: InStock
Author: shynlee04

Identify missing information, unknown dependencies, and risks across eight dimensions before development.

Updated Feb 5, 2026

Search Tags:#gap analysis #risk assessment #pre-implementation #dependency mapping #proactive development #unknowns identification

Ready to run

npx skills add https://github.com/shynlee04/idumb-v2 --skill gap-analysis-shynlee04

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gap-analysis
Source: https://github.com/shynlee04/idumb-v2/tree/main/.agents/skills/gap-analysis
Command: npx skills add https://github.com/shynlee04/idumb-v2 --skill gap-analysis-shynlee04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill systematically identifies missing information, unknown dependencies, and potential risks before starting a new task or making changes, preventing costly mistakes and rework.

Core Features & Use Cases

Proactive Gap Identification: Ensures all critical areas (context, knowledge, integration, dependencies, constraints, validation, rollback, documentation) are considered.
Structured Investigation: Provides a clear framework and actionable steps to investigate identified gaps.
Use Case: Before implementing a new feature, use this skill to ensure you've considered all existing systems, potential integration issues, and necessary validation steps, leading to a smoother development process.

Quick Start

Use the gap-analysis skill to identify potential issues before refactoring the user module.

Frequently Asked Questions about gap-analysis

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

FAQPage Schema

How do I identify unknown dependencies before starting development?▼

To identify unknown dependencies before development, systematically map the current state and categorize gaps across context, knowledge, integration, constraints, and validation dimensions, then prioritize them by impact to create a structured investigation plan.

What is the best way to assess risks before refactoring a module?▼

The best way to assess risks before refactoring is to map the current state, identify missing knowledge and constraints, categorize potential integration issues, and create a prioritized investigation plan to resolve unknowns proactively.

What's the best way to map missing information before architectural changes?▼

The best way to map missing information before architectural changes is to systematically evaluate eight dimensions including context, knowledge, integration, dependencies, constraints, validation, rollback, and documentation, then prioritize discovered gaps by their potential impact.

When do I need a structured gap analysis for proactive development?▼

You need a structured gap analysis for proactive development when implementing a new feature or making architectural changes, ensuring you proactively consider existing systems, integration issues, and necessary validation steps before coding begins.

How do I create an investigation plan for pre-implementation unknowns?▼

Create an investigation plan for pre-implementation unknowns by mapping the current state, categorizing identified gaps across eight critical dimensions, prioritizing them by impact, and defining actionable steps to investigate each risk before coding.

Does gap analysis cover rollback and documentation risks?▼

Yes, gap analysis covers rollback and documentation risks by systematically evaluating eight dimensions including context, knowledge, integration, dependencies, constraints, validation, rollback, and documentation to ensure comprehensive risk assessment before development.