agentleFS
HHC225HHC225/Japanese-Client-Breaker/.claude/skills/03_gap-analysis/skill.md

gap-analysis

Skill2 starsChanged 7 months agoMITView on GitHub

Identifies what is MISSING from a deliverable — gaps in structure, stakeholder coverage, scenarios, risks, evidence, and regulatory considerations. Runs in parallel with the Analyst. Use when checking deliverable completeness or detecting blind spots.

21 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the preprocessed deliverable

    line 22

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

Gap Analysis Skill

{WORKSPACE} = timestamped run directory provided by the orchestrator.

Purpose

Detect blind spots. The Analyst extracts what the deliverable contains; the Gap Analyzer identifies what it SHOULD contain but doesn't. These two tasks are independent and run in parallel.

When to Use

  • Any deliverable needs completeness assessment
  • Need to identify missing sections, unconsidered scenarios, absent stakeholders
  • Preparing for a review where "why didn't you consider X?" questions are expected

Process

  1. Read the preprocessed deliverable
  2. Identify the deliverable type (test plan, design doc, proposal, report)
  3. Apply the 6-dimension gap analysis framework
  4. Score each gap by severity (CRITICAL / IMPORTANT / NICE_TO_HAVE)
  5. Identify missing stakeholder perspectives
  6. Output structured gap report

Integration with Pipeline

  • Runs at: Phase 1 (parallel with Analyst)
  • No dependency on Analyst — reads preprocessed input directly
  • Feeds into: Phase 1.5 (Decision Advisor may reference gaps), Phase 2 (Critic incorporates gap findings), Phase 4 (QA validates gap analysis)
  • Report: Gaps appear in a dedicated "Gaps" section with different visual treatment from criticism findings

Quality Checklist

  • All 6 dimensions analyzed (structural, stakeholder, scenario, risk, evidence, regulatory)
  • Each gap has a specific recommendation (not just "add this")
  • Severity classifications are justified
  • Missing perspectives identified with specific "what they would flag"
  • Completeness score calculated with rationale

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.