One-click install
npx skills add https://github.com/testdouble/han --skill gap-analysis-testdouble
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-analysis
Source: https://github.com/testdouble/han/tree/main/han-core/skills/gap-analysis
Command: npx skills add https://github.com/testdouble/han --skill gap-analysis-testdouble

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gap-analysis helps teams compare a current state against a desired state to identify discrepancies and produce a clear, stakeholder-friendly report. It focuses on artifact-level alignment and does not diagnose runtime bugs, architectural decisions, or open-ended option exploration.

Core Features & Use Cases

  • Compares two artifacts (e.g., code, docs) and lists gaps with stable IDs.
  • Produces plain-language executive summaries and detailed gap entries for planning and remediation.
  • Generates structured output suitable for tickets, docs, and reviews.

Quick Start

Compare your current artifact with the desired artifact and run the gap-analysis to generate a report.

Frequently Asked Questions about gap-analysis

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

FAQPage Schema
How do I compare current documentation against a desired state to find gaps?

Gap analysis compares a current artifact against a corresponding desired state artifact, identifying discrepancies and producing a structured gap report with stable IDs to guide stakeholder-driven remediation and planning.

How do I generate a structured gap report for stakeholder remediation planning?

Gap analysis produces a structured gap report with stable IDs, plain-language executive summaries, and detailed gap entries suitable for ticketing, documentation, and stakeholder reviews from two compared artifacts.

Can I use artifact comparison to identify discrepancies in software features and processes?

Yes, artifact comparison identifies discrepancies in software features, docs, processes, and designs by evaluating a current artifact against a desired state, producing a structured plan for stakeholder-driven remediation.

Do I need clearly defined current and desired state artifacts to run a gap analysis?

Yes, gap analysis requires a clearly defined current state artifact and a corresponding desired state artifact to produce a structured comparison output suitable for ticketing and stakeholder review.

What are the limitations of using gap analysis for software engineering planning?

Gap analysis focuses on artifact-level alignment and does not diagnose runtime bugs, architectural decisions, or open-ended option exploration, limiting its use to structured comparisons between defined current and desired states.