Home / qa-aman / claude-skills · GitHub

gap-analysis SKILL.md skillA

gap-analysis from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add qa-aman/claude-skills/gap-analysis@git:20260323.771ca1c

Pins git:20260323.771ca1c in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: qa-aman/claude-skills
Path: skills/by-role/business-analyst/gap-analysis/SKILL.md
Versions recorded: 1
Latest version: git:20260323.771ca1c, committed Mar 23, 2026
Size: 5,489 bytes
Repository stars: 21
License: MIT

Identify gaps between current and desired state. Use when the user says "gap analysis", "what's missing", "current vs future state", "where are the gaps", "capability gap", "maturity assessment", "fit-gap analysis", "what needs to change", "compare current to target", "readiness assessment" - even if they don't explicitly say "gap analysis".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

## Overview

Based on the **BABOK Guide v3 (IIBA)** - Strategy Analysis knowledge area, which defines gap analysis as the comparison between current state and desired future state to identify changes needed. Also draws on **Mastering the Requirements Process** by Suzanne & James Robertson for the Brown Cow Model - a 2x2 matrix (What/How x Now/Future) that prevents teams from jumping to solutions before understanding the problem space. The key insight: gap analysis must cover all four quadrants of the Brown Cow Model. Teams that skip "What-Now" (current business requirements) and jump straight to "How-Future" (new system design) build the wrong thing.

## Workflow

### Step 1: Define the desired future state
Document what success looks like using measurable targets:
```
FUTURE STATE OBJECTIVE: [what capability or performance level is needed]
BUSINESS DRIVER: [why this change is needed now]
SUCCESS METRIC: [how we will know we've arrived]
TARGET DATE: [when this must be achieved]
```

### Step 2: Document the current state using Brown Cow Model
Map all four quadrants:
```
|           | WHAT (requirements)        | HOW (implementation)         |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add qa-aman/claude-skills/gap-analysis@sha256:ec32d4babd89da1e

The line at the top of this page pins the label git:20260323.771ca1c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_3w7ruv7sfr25zzk2.svg)](https://markdownregistry.com/a/art_3w7ruv7sfr25zzk2)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Mar 23, 2026.

version	committed	commit	size	audit
git:20260323.771ca1c latest	2026-03-23	771ca1c	5,489 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5489 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_3w7ruv7sfr25zzk2
GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/gap-analysis
GET https://markdownregistry.com/api/v1/blob/ec32d4babd89da1e945119b656c2406bdc6b2baa336dd16fc95b5a02311b84b4

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from qa-aman/claude-skills

create-skill SKILL.md skill

qa-aman/claude-skills · .claude/skills/create-skill/SKILL.md · Create or update Claude Code skills following Anthropic's official skill standard. Use when user says "create a skill"…

git:20260303.4fa499f · audit A · 21 stars

sync-skills SKILL.md skill

qa-aman/claude-skills · .claude/skills/sync-skills/SKILL.md · Fetch skills from projects on the current system, genericize them, and add to the claude-skills repository. Use when…

git:20260303.4fa499f · audit A · 21 stars

CLAUDE.md CLAUDE.md file

qa-aman/claude-skills · CLAUDE.md

git:20260808.3d6e28d · audit A · 21 stars

audit-workpaper SKILL.md skill

qa-aman/claude-skills · skills/by-role/accountant/audit-workpaper/SKILL.md · Write a clear, reviewable audit workpaper documenting procedures, evidence, and conclusions. Use when an auditor says…