gap-analysis

Analyze gaps between requirements and the current codebase.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/sizukutamago/blueprint-plugin --skill gap-analysis-sizukutamago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-analysis
Source: https://github.com/sizukutamago/blueprint-plugin/tree/main/skills/gap-analysis
Command: npx skills add https://github.com/sizukutamago/blueprint-plugin --skill gap-analysis-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analyzes gaps between requirements and the current codebase to inform implementation strategy.

Core Features & Use Cases

  • Current state assessment: compare documented requirements with existing code structures and artifacts.
  • Feasibility and option assessment: evaluate viability of implementation approaches and surface alternatives.
  • Stakeholder guidance: provide actionable plans for architecture, data models, APIs, and UI changes.

Quick Start

Run the gap-analysis skill to compare docs/requirements/user-stories.md with the codebase and generate docs/00_analysis/gap_analysis.md.

Frequently Asked Questions about gap-analysis

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

FAQPage Schema
How do I identify gaps between project requirements and my current codebase?

Gap-analysis identifies discrepancies between requirements and your codebase by comparing documented user stories with existing architecture, data models, APIs, and UI, outputting a structured report of required changes, recommended options, and risks.

Can I assess project feasibility by comparing user stories against existing code?

Yes, assessing project feasibility involves comparing documented user stories against existing code artifacts to evaluate implementation viability and surface alternative architectural approaches.

What is the best way to plan implementation changes for architecture, data models, and APIs?

Planning implementation changes is best achieved by running a gap-analysis that evaluates required modifications across architecture, data models, APIs, and UI, yielding actionable stakeholder guidance.

How do I generate a gap-analysis report for my software project?

To generate a gap-analysis report, compare your requirements documentation with the codebase to output a structured markdown file at docs/00_analysis/gap_analysis.md detailing recommended options, risks, and required artifacts.

Does gap-analysis require any specific dependencies to evaluate codebase readiness?

No, gap-analysis requires zero external dependencies to evaluate codebase readiness, relying solely on comparing existing requirements documentation with current code structures to identify implementation gaps.