gap-resolver

Prioritize LLM user-testing gaps and drive fix-verify cycles.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/dhamija/claude-workflow-agents --skill gap-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-resolver
Source: https://github.com/dhamija/claude-workflow-agents/tree/main/templates/skills/gap-resolver
Command: npx skills add https://github.com/dhamija/claude-workflow-agents --skill gap-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically surfaces and prioritizes gaps identified during LLM user testing, enabling structured fixes and measured improvements to promised outcomes.

Core Features & Use Cases

  • Gap prioritization: Rank issues by severity, impact, and effort to focus on the most impactful fixes.
  • Fix specification and orchestration: Generate detailed fix specs, assign tasks, and manage dependencies across backend, frontend, and testing work.
  • Iterative verification: Re-run evaluation with LLM users to validate that fixes meet acceptance criteria and fulfill promises.
  • Promote accountability: Track progress from discovery through validation and update promises accordingly.

Quick Start

Use this skill to analyze a failing user-test scenario, create a fix spec, and drive a verification cycle to validate a promise.

Frequently Asked Questions about gap-resolver

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

FAQPage Schema
How do I identify and prioritize gaps from LLM user testing?

Gap prioritization ranks issues by severity, impact, and effort to focus fixes on the most impactful problems. This surfaces gaps revealed during LLM testing and structures which fixes to address first, enabling systematic improvement of promised outcomes across multiple user scenarios.

How do I create a fix specification and track dependencies across teams?

Fix specification orchestration generates detailed specs, assigns tasks, and manages dependencies across backend, frontend, and testing work. This centralizes fix tracking from discovery through implementation, ensuring accountability and progress visibility across multiple personas and development areas.

Can I verify that fixes actually meet acceptance criteria after implementation?

Iterative verification re-runs evaluation with LLM users to validate that fixes fulfill promised outcomes and meet acceptance criteria. This completes test-fix-verify cycles, confirming improvements before updating promises and closing gaps.

What's the best way to manage end-to-end workflows from testing through validation?

Structured workflow management enforces a complete cycle: generate fix specifications, track task dependencies, implement changes, and verify validation through iterative testing. This maintains accountability from gap discovery to promise validation across design, development, and verification stages.

Do I need to run multiple test cycles to confirm gaps are fixed?

Yes. Iterative verification cycles with LLM users validate that fixes address the original gaps and meet acceptance criteria. Multiple cycles ensure fixes don't introduce regressions and that promised outcomes are actually delivered before closing the gap.