analyzing-gaps

Compare UTC expectations against reality files to generate structured gap reports.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/0xHoneyJar/construct-observer --skill analyzing-gaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-gaps
Source: https://github.com/0xHoneyJar/construct-observer/tree/main/skills/analyzing-gaps
Command: npx skills add https://github.com/0xHoneyJar/construct-observer --skill analyzing-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gaps between user expectations captured in UTCs and observed code behavior in reality files can obscure product risks and delay improvements.

Core Features & Use Cases

  • Load and parse journeys and canvases to extract JTBD and expectation gaps
  • Compare against code reality to generate structured gap reports with severity and recommendations
  • Produce linked artifact outputs and update frontier state artifacts for traceability

Quick Start

Run the gap analysis for a journey to generate and review its gap report

Frequently Asked Questions about analyzing-gaps

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

FAQPage Schema
How do I identify gaps between user expectations and actual code behavior?

To identify gaps between user expectations and actual code behavior, compare user journey canvases against reality files to generate a structured gap report with severity ratings and recommendations.

What is a gap analysis report and when do I need one?

A gap analysis report documents discrepancies between expected user experiences and real code behavior. You need one when product risks from mismatched expectations delay improvements and require severity mapping.

How do I generate a gap report with JTBD impact mapping for my project?

Generate a gap report with JTBD impact mapping by loading journeys and canvases to extract expectations, comparing them against code reality files, and outputting a structured markdown report with YAML frontmatter metadata.

Can I use gap analysis for journeys without linked canvases or reality files?

No, gap analysis applies specifically to journeys with linked canvases and reality files. These linked artifacts are required to extract expectations, compare code behavior, and update frontier state artifacts for traceability.

What's the best way to document product risks from expectation mismatches?

The best way to document product risks from expectation mismatches is using a structured gap report enforcing a taxonomy of gap types and severities, mapping JTBD impacts, and updating linked artifacts for full traceability.

How does severity mapping work when comparing user expectations to code reality?

Severity mapping works by enforcing a predefined taxonomy of gap types and severities onto identified discrepancies, mapping their impact on Jobs-To-Be-Done, and producing structured recommendations within a markdown gap report.