implementation-gap-analysis

Analyze task inputs and current codebase to document implementation gaps.

282|20|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/TheSoftwareHouse/copilot-collections --skill implementation-gap-analysis-thesoftwarehouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-gap-analysis
Source: https://github.com/TheSoftwareHouse/copilot-collections/tree/main/.github/skills/implementation-gap-analysis
Command: npx skills add https://github.com/TheSoftwareHouse/copilot-collections --skill implementation-gap-analysis-thesoftwarehouse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify and document gaps between the current system state and intended changes, ensuring nothing is missed during delivery.

Core Features & Use Cases

  • Completes a structured analysis by reviewing task inputs, current codebase, and planned changes to determine what must be created, what must be modified, and what can be reused.
  • Generates a formal Implementation Gap Analysis report using a defined template to communicate scope, effort, and risks across stakeholders.

Quick Start

Run the analysis to identify gaps by comparing the current implementation state to the planned changes.

Frequently Asked Questions about implementation-gap-analysis

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

FAQPage Schema
How do I identify gaps between planned changes and my current codebase?

Implementation gap analysis identifies gaps by comparing task inputs and planned changes against your current system, determining what must be created, modified, or reused to ensure accurate delivery.

What is an implementation gap analysis report used for in software projects?

An implementation gap analysis report communicates scope, effort, and risks across stakeholders, using a template-driven summary to document differences between the current system state and intended changes.

How do I document what needs to be created or modified before delivering software changes?

Document required changes by running a structured analysis that reviews task inputs and the current codebase, categorizing elements into items to create, modify, or reuse within a formal gap report.

Can I use a template-driven workflow for stakeholder alignment on implementation gaps?

Yes, this process provides a template-driven final summary and a structured gap-report workflow to facilitate stakeholder alignment by clearly mapping implementation gaps against planned changes.

When do I need an implementation gap analysis for my software project?

You need an implementation gap analysis when planning changes to an existing system, ensuring nothing is missed during delivery by mapping the differences between the current state and intended updates.