gap-analysis

Compare codebase specifications against implementation to identify gaps and generate roadmaps.

1|Updated Jan 24, 2026

Search Tags:#code analysis #gap analysis #spec-driven development #brownfield #greenfield

Ready to run

npx skills add https://github.com/johan--/stackshift --skill gap-analysis-johan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ast, specification-checking, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the gap analysis for codebases, simplifying the process of identifying discrepancies between specifications and implementation, thus enhancing spec-driven development.

Core Features & Use Cases

Route-aware Gap Analysis: Analyzes codebases against specifications, distinguishing between greenfield (new app development) and brownfield (existing app management).
Greenfield Route: Validates spec completeness for new applications and determines target tech stacks.
Brownfield Route: Identifies gaps between existing code and specifications, utilizing AST-powered analysis.
Automated Roadmap Creation: Generates implementation roadmaps based on identified gaps and priorities.

Quick Start

Execute the gap-analysis skill to start the automated gap analysis process.

Frequently Asked Questions about gap-analysis

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

FAQPage Schema

How do I automate gap analysis between my project specifications and codebase implementation?▼

To automate gap analysis between specifications and implementation, you can use a route-aware tool that compares your codebase against defined specs. It distinguishes between new app development and existing app management to produce detailed gap reports and implementation roadmaps.

How does AST-powered analysis identify gaps in existing applications?▼

AST-powered analysis identifies gaps in existing applications by parsing the codebase structure and comparing it directly against your specifications. This brownfield route detects discrepancies between the actual code and the required spec-driven implementation.

What is the difference between greenfield and brownfield gap analysis routes?▼

The greenfield route validates spec completeness and determines target tech stacks for new applications, while the brownfield route uses AST-powered analysis to identify implementation gaps in existing codebases against current specifications.

Can I generate an implementation roadmap from identified codebase gaps?▼

Yes, you can generate an implementation roadmap from identified codebase gaps. The analysis automatically creates an implementation roadmap based on the discovered discrepancies between specifications and implementation, prioritized for your development workflow.

Does gap analysis work with specification-checking for spec-driven development?▼

Yes, gap analysis integrates with specification-checking dependencies to support spec-driven development. It leverages these checks to validate greenfield specs and compare brownfield codebases against your defined requirements.

When should I use automated gap analysis for a new application?▼

You should use automated gap analysis for a new application when you need to validate spec completeness and determine your target tech stacks. The greenfield route ensures your specifications are fully ready before implementation begins.