skills.rest
benediktms
benediktmsCOMMUNITY
Explore all skills by this author →
Website𝕏@benediktmsGitHub

lacuna

Identify gaps between stated objectives and delivered implementations in specs, tickets, and PRs.

Updated Mar 26, 2026
Search Tags:#documentation#requirements#spec#code-review#acceptance-criteria#gap-analysis#lacuna
One-click install
npx skills add https://github.com/benediktms/overmind --skill lacuna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lacuna
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/lacuna
Command: npx skills add https://github.com/benediktms/overmind --skill lacuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The lacuna persona reads the stated objective (task description, ticket, plan, or PR description) and finds what was promised but not delivered: missing endpoints, unhandled acceptance-criteria branches, undocumented behavior changes, partial migrations, and declared-but-unwired flags or error paths. Use after implementation is complete to surface gaps before merge.

Core Features & Use Cases

  • Gap analysis of specifications, tickets, PRs, and plans to surface missing or incomplete work.
  • Detect unhandled acceptance criteria, undocumented changes, and partial migrations.
  • Identify declared-but-not-wired flags or error paths and documentation drift.
  • Provide concrete guidance on where the spec is unmet to inform reviews and merges.

Quick Start

Provide the stated objective, ticket, plan, or PR description and let lacuna surface the gaps before merge.

Frequently Asked Questions about lacuna

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

FAQPage Schema
How do I identify gaps between spec and implementation before merging?▼

Gap analysis compares stated objectives like tickets or specs against delivered code to surface missing endpoints, unhandled acceptance criteria, and undocumented behavior changes before merge. It reviews APIs, migrations, and feature flags to find where the spec is unmet.

What is documentation drift and how do I detect it in a pull request?▼

Documentation drift occurs when code changes are not reflected in specs or PR descriptions. Gap analysis detects this drift by comparing the stated PR objectives against the implementation to surface undocumented behavior changes and missing functionality.

How do I find unhandled acceptance criteria and partial migrations in code review?▼

Gap analysis during code review reads acceptance criteria and plans to detect partial migrations, unhandled branches, and declared-but-unwired flags. It provides concrete guidance on exactly where the delivered implementation fails to meet the spec.

Can I check for declared but unwired feature flags and missing endpoints?▼

Yes, gap analysis applies to specifications and PR descriptions to identify declared-but-unwired feature flags, missing API endpoints, and unhandled error paths. It enforces detection of these gaps to inform code reviews prior to merge.

Does gap analysis work for API specs, database migrations, and feature flags?▼

Gap analysis works across APIs, database migrations, and feature flags to surface missing endpoints, partial migrations, and undocumented changes. It reads stated objectives from tickets or plans to enforce detection of missing functionality.

Related Skills

Explore More Software Engineering Skills→
alfredoperezalfredoperez
80

to-tickets

Create tickets with dependencies from plans, specs, or conversations.

Community
Intermediate
FutureAtomsFutureAtoms

arch-compliance

Audit Kartix implementation against documentation and classify feature reality.

Community
Advanced
KjellKodKjellKod
36

code-reviewer

Analyze pull request changes against acceptance criteria for Python, JavaScript, TypeScript, and React.

Community
Basic
AribSudiaAribSudia
2

arib-docs-api

Scan Express, FastAPI, and Django codebases to validate API endpoints against OpenAPI specifications.

Community
Advanced