What output does this skill produce?

It generates a detailed report at docs/gap-analysis-report.md that includes a phased roadmap, priority levels (P0-P3), and a thorough catalog of technical debt.

What is the difference between Greenfield and Brownfield routes?

Greenfield is for new projects where the skill validates specification completeness and tech stack selection, while Brownfield compares specs against an existing codebase to find missing or partial implementations.

How does the AST analysis work?

It performs a deep inspection of your source code to verify function signatures, detect placeholder stubs, identify missing parameters, and estimate implementation effort with a high confidence score.

Do I need to run other skills before this one?

Yes, this is Step 4 of the StackShift process. You must have already completed Step 1 (Analyze) to set the project route and Step 3 (Create Specs) to provide the baseline for comparison.

Gap Analysis (Route-Aware)

Name: Gap Analysis (Route-Aware)
Author: jschulte

byjschulte

•

Developer Tools

Identifies functional discrepancies between project specifications and code implementations using AST-powered analysis.

The Gap Analysis skill is a critical component of the StackShift workflow, designed to bridge the gap between requirements and reality. It performs route-aware analysis for both Greenfield (new) and Brownfield (legacy) projects, utilizing Abstract Syntax Tree (AST) inspection to detect missing features, partial implementations, and code stubs. By automating the comparison of specifications against actual code, it provides developers with a prioritized implementation roadmap (P0-P3), technical debt assessments, and a structured report to guide the development process from reverse engineering to full feature parity.

Key Features

01Priority-based task categorization (P0-P3) to identify critical blockers and high-impact features.

02Automated generation of a comprehensive gap-analysis-report.md with phased roadmaps.

03Fallback analysis modes including Spec Kit integration and manual specification review.

04AST-powered code inspection for deep verification of function signatures and business logic.

051 GitHub stars

06Dual-route logic for validating new project specs or analyzing existing legacy codebases.

Use Cases

01Validating the completeness of user stories and acceptance criteria before starting a new build.

02Auditing legacy codebases to determine which features match the documented specifications.

03Mapping technical debt and missing test coverage during the refactoring of brownfield applications.

Key Features

01Priority-based task categorization (P0-P3) to identify critical blockers and high-impact features.

02Automated generation of a comprehensive gap-analysis-report.md with phased roadmaps.

03Fallback analysis modes including Spec Kit integration and manual specification review.

04AST-powered code inspection for deep verification of function signatures and business logic.

051 GitHub stars

06Dual-route logic for validating new project specs or analyzing existing legacy codebases.

Use Cases

01Validating the completeness of user stories and acceptance criteria before starting a new build.

02Auditing legacy codebases to determine which features match the documented specifications.

03Mapping technical debt and missing test coverage during the refactoring of brownfield applications.