sdd-validate-gap

Analyze implementation gaps between project requirements and existing codebases.

Updated Dec 2, 2025

Search Tags:#technical debt #codebase analysis #gap analysis #requirements validation #implementation strategy #brownfield development

Ready to run

npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-validate-gap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-validate-gap
Source: https://github.com/qlawmarq/dotfiles-common/tree/main/skills/sdd-init/references/skills/validate-gap
Command: npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-validate-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of understanding the discrepancies between project requirements and an existing codebase, particularly in complex brownfield development scenarios.

Core Features & Use Cases

Gap Analysis: Identifies missing functionalities and integration challenges by comparing requirements against the current codebase.
Approach Evaluation: Assesses multiple strategies for implementing new features, such as extending existing modules or building new components.
Use Case: Before starting a new feature development on a legacy system, use this skill to understand exactly what needs to be built, what existing code can be leveraged, and what the potential roadblocks are.

Quick Start

Use the sdd-validate-gap skill to analyze the implementation gap for the 'user-authentication' feature.

Frequently Asked Questions about sdd-validate-gap

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

FAQPage Schema

How do I analyze the implementation gap between project requirements and an existing codebase?▼

To analyze the implementation gap, compare detailed feature specifications and requirements.md against current code patterns and external dependencies to identify missing capabilities and integration challenges in brownfield development.

What is requirements validation for brownfield development?▼

Requirements validation for brownfield development is the process of evaluating project requirements against an existing codebase to pinpoint missing functionalities, assess technical debt, and determine integration challenges before building new features.

How do I evaluate multiple implementation approaches for a legacy codebase?▼

Evaluate multiple implementation approaches by comparing feature specifications against existing code patterns and external dependencies to assess whether extending current modules or building new components is the most viable strategy.

Do I need spec.json and requirements.md to perform gap analysis?▼

Yes, detailed analysis of spec.json, requirements.md, and steering context files is required to accurately identify missing capabilities and integration challenges within an existing codebase.

What's the best way to identify missing capabilities before extending a legacy system?▼

The best way to identify missing capabilities is to perform a gap analysis that directly compares your new feature specifications against the current codebase patterns and external dependencies to uncover roadblocks.

When should I not use gap analysis for feature development?▼

Gap analysis is not suitable for greenfield projects lacking an existing codebase, as it specifically requires current code patterns and external dependencies to evaluate implementation strategies and identify discrepancies.