Reverse Engineering Business Logic
Reverse engineers business logic from source code by extracting operational business truth. Use when user asks to understand what the system actually does, analyze business rules, extract domain logic, infer workflows from code, explain state transitions, or identify decision logic. Works with API views (Django, FastAPI, etc.), domain models, background tasks, and multi-step workflows.
Install
npx skills add meirm/reverse-engineering-skill --skill reverse-engineering-business-logicgit 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/reverse-engineering-business-logic ~/.claude/skills/reverse-engineering-business-logicPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Reverse Engineer Business Logic from Code ## Project setup This skill is **project-agnostic**. Before use, ensure the project has a BDD config so output paths and terminology are defined. If `BDD/project_config.yaml` (or `.cursor/bdd_project_config.yaml`) exists, read it for `bl_output.root`, `bl_output.categories`, and `terminology`. If not, run the **tailor-bdd-skills-for-project** skill first to create it. **Default when no config exists:** write BL under `business_logic/` with categories `endpoints`, `models`, `workflows`, `billing`. --- ## Quick Start (5 minutes) Extract business logic from code in 3 steps: **1. Say** "extract business logic from [file/function/feature]" - Example: "extract business logic from order creation" - Example: "explain what the payment charging flow actually does" **2. Review** the generated markdown in the BL output directory (from project config, or `business_logic/`) - 11 sections covering purpose, actors, flow, rules, billing, edge cases - All with line number references to source code **3. Verify** completeness using the validation checklist (below) **Where outputs go (organized by state):** Use paths from project config `bl_output` when present; otherwise: - **Current production code** → `[bl_root]/current/[category]/[name].md` - **Proposed changes** → `[bl_root]/proposal/[category]/[name].md` - **Work in progress** → `[bl_root]/under_development/[category]/[name].md`
Details
- Skill name
reverse-engineering-business-logic- Repository
- meirm/reverse-engineering-skill
- Path
skills/reverse-engineering-business-logic/SKILL.md- License
- MIT
- Repo updated
- 2 October 2026
FAQ
What does the Reverse Engineering Business Logic skill do?
Reverse engineers business logic from source code by extracting operational business truth. Use when user asks to understand what the system actually does, analyze business rules, extract domain logic, infer workflows from code, explain state transitions, or identify decision logic. Works with API views (Django, FastAPI, etc.), domain models, background tasks, and multi-step workflows.
How do I install the Reverse Engineering Business Logic skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add meirm/reverse-engineering-skill --skill reverse-engineering-business-logic. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Reverse Engineering Business Logic popular?
It lives in meirm/reverse-engineering-skill, which has 47 GitHub stars and 7 forks.
Related skills
Analyze Business Logic Gaps
47meirm/reverse-engineering-skill
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.
Bdd Orchestrator
47meirm/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.
Derive Acceptance Criteria From Business Logic
47meirm/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.
Customer Context
49Dan-Cleary/fdestack
Load a customer's context at the start of every session. Run this before any other FDEstack skill. Reads all 7 context files, surfaces drift since last session, asks what's new, and commits updates. Proactively invoke this skill (do NOT answer customer-specific questions directly) when the user references a customer name in an FDE ops repo without context being loaded this session. Always the first skill in a customer session — every other FDEstack skill requires its session marker. Usage: /customer-context <customer-name> Voice triggers: "load <customer>", "start session with <customer>", "wh
Refine Business Logic for Implementation
47meirm/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.
Discovery
49Dan-Cleary/fdestack
Process any inbound source of customer context — meeting transcript, prior FDE's handoff notes, AE/sales briefing, customer-side RFP response, prior Discovery Workshop output, or your own raw notes. Extracts new stack info, stakeholders, stated problem, real problem, open questions, and context conflicts. Updates customer context files and commits. Proactively invoke this skill (do NOT just summarize) when the user pastes call notes, meeting transcripts, AE briefings, RFP responses, handoff docs, or any inbound document about a customer. Triggers on phrases like "I just had a meeting", "here a
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.