Analyze Business Logic Gaps

Identifies missing, vague, underspecified, or contradictory business logic within BL documents. Finds incomplete edge cases, missing state transitions, ambiguous terminology, and weak billing rules. Use when reviewing business logic quality, hardening requirements, or preparing BL for implementation.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add meirm/reverse-engineering-skill --skill analyze-business-logic-gaps
Manual install
git clone --depth 1 https://github.com/meirm/reverse-engineering-skill.git /tmp/reverse-engineering-skill
mkdir -p ~/.claude/skills
cp -r /tmp/reverse-engineering-skill/skills/analyze-business-logic-gaps ~/.claude/skills/analyze-business-logic-gaps

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Analyzing Business Logic Gaps

**Project-agnostic.** For consistent domain terms when reporting gaps, use `BDD/project_config.yaml` → `terminology` if present (see **tailor-bdd-skills-for-project**).

## Purpose

Find weaknesses in business logic documentation that could lead to implementation bugs, billing errors, or ambiguous behavior. This is a requirements-hardening skill.

## Prerequisites

- A business logic document to analyze
- Understanding of the problem domain
- Access to related documentation (API specs, existing code)

## Instructions

### Step 1: Read and Parse the BL Document

```bash
cat path/to/bl_document.md
```

Extract all stated rules, workflows, and behaviors.

### Step 2: Apply Gap Detection Categories

Systematically check the BL for gaps in these areas:

#### A. Entry and Exit Conditions

**Questions to ask:**
- Are all preconditions for each operation specified?
- Are all possible exit states defined?
- What happens when preconditions are not met?

**Look for:**
- Missing input validation rules
- Undefined behavior for edge cases (null, empty, invalid values)
- Unspecified cleanup or rollback on failure

#### B. State Definitions

**Questions to ask:**
- Are all possible states explicitly listed?
- Is each state's meaning clearly defined?
- Are states mutually exclusive and collectively exhaustive?

**Look for:**
- References to states not in the state definition list
- Ambiguous state names ("processed", "handled", "pending")
Read the full skill on GitHub

Details

Skill name
analyze-business-logic-gaps
Path
skills/analyze-business-logic-gaps/SKILL.md
License
MIT
Repo updated
2 October 2026

FAQ

What does the Analyze Business Logic Gaps skill do?

Identifies missing, vague, underspecified, or contradictory business logic within BL documents. Finds incomplete edge cases, missing state transitions, ambiguous terminology, and weak billing rules. Use when reviewing business logic quality, hardening requirements, or preparing BL for implementation.

How do I install the Analyze Business Logic Gaps skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add meirm/reverse-engineering-skill --skill analyze-business-logic-gaps. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Analyze Business Logic Gaps popular?

It lives in meirm/reverse-engineering-skill, which has 47 GitHub stars and 7 forks.

Related skills

Bdd Orchestrator

47

meirm/reverse-engineering-skill

Orchestrates the full BDD workflow from code to trustworthy business logic — extraction, validation, gap analysis, refinement, acceptance criteria, and test generation. Use when the user requests comprehensive analysis like "understand [feature] from code", "analyze [domain] end-to-end", or "prepare [feature] for implementation or sprint planning", coordinating the other BDD skills step by step.

Testing & QA

Derive Acceptance Criteria From Business Logic

47

meirm/reverse-engineering-skill

Converts trusted business logic into product-owner-grade acceptance criteria and developer-ready tasks using Given/When/Then scenarios. Use when creating user stories, preparing for sprints, or turning BL into executable requirements.

Marketing, Sales & Business

Generate Tests From Business Logic

47

meirm/reverse-engineering-skill

Generates scenario tests, rule tests, edge case tests, state transition tests, and billing tests from trusted business logic. Use when creating test suites from BL, ensuring BL coverage, or turning requirements into verifiable tests.

Testing & QA

Plan Marketing Campaigns

40

makenotion/cursor-notion-plugin

Organize campaign briefs, content ideas, and production work in Notion. Use when planning a marketing campaign, building a content calendar, or tracking content production.

Marketing, Sales & BusinessIn 1 list21

Refine Business Logic for Implementation

47

meirm/reverse-engineering-skill

Rewrites vague business logic into deterministic, testable rules by separating policy from mechanism, normalizing terminology, and defining explicit state machines. Use when preparing BL for code implementation, making BL executable, or normalizing ambiguous requirements.

Marketing, Sales & Business

Suggestion

113

Hmbown/Wizards-of-the-Ghosts

Suggestion is about the craft of the single nudge — not campaigns, not arguments, not automation. It produces one carefully placed prompt at the moment a user is most receptive. The planted idea must be reasonable and defensible. If the user would feel manipulated upon learning how it was designed, the spell refuses.

Marketing, Sales & Business11

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.