Validate Business Logic Against Code
Verifies whether documented business logic is actually implemented by mapping BL rules to code evidence. Flags rules as implemented, partially implemented, contradicted, or not found. Use when validating business logic documents, checking code coverage against requirements, or verifying BL-to-code alignment.
Install
npx skills add meirm/reverse-engineering-skill --skill validate-business-logic-against-codegit 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/validate-business-logic-against-code ~/.claude/skills/validate-business-logic-against-codePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Validating Business Logic Against Code **Project-agnostic.** Use `BDD/project_config.yaml` → `bl_output.root` and `validation` (or `entry_points`) for BL and code paths when present (see **tailor-bdd-skills-for-project**). ## Purpose Build trust between documented business logic and actual implementation by systematically mapping each BL rule to concrete evidence in the codebase. ## Prerequisites - A business logic document (markdown, YAML, or structured text) - Access to the relevant code files - Understanding of the project structure ## Instructions ### Step 1: Parse Business Logic Document Read the BL document and extract all explicit rules: ```bash # Read the BL document cat path/to/bl_document.md ``` Extract and categorize rules: - **Validation rules**: What conditions are checked - **State transition rules**: How state changes - **Billing/credit rules**: When charges occur - **Error handling rules**: How failures are processed - **Workflow rules**: Sequential/parallel operations - **Routing/fallback rules**: Provider selection logic ### Step 2: Identify Relevant Code Files For each rule category, identify the code files that would implement it: ```bash # Search for relevant code grep -r "keyword" django_app/ ``` **Common mapping (adapt to your project):** - Validation rules → views, serializers, validators - State transitions → models, state handlers - Billing rules → billing/ledger services, models - Error handling → views, task handlers
Details
- Skill name
validate-business-logic-against-code- Repository
- meirm/reverse-engineering-skill
- Path
skills/validate-business-logic-against-code/SKILL.md- License
- MIT
- Repo updated
- 2 October 2026
FAQ
What does the Validate Business Logic Against Code skill do?
Verifies whether documented business logic is actually implemented by mapping BL rules to code evidence. Flags rules as implemented, partially implemented, contradicted, or not found. Use when validating business logic documents, checking code coverage against requirements, or verifying BL-to-code alignment.
How do I install the Validate Business Logic Against Code skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add meirm/reverse-engineering-skill --skill validate-business-logic-against-code. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Validate Business Logic Against Code 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.
Poc
49Dan-Cleary/fdestack
Build a throwaway proof-of-concept. Speed over quality. Hardcoded values OK, ugly code OK, no error handling beyond crash prevention. This code is NEVER going to production — /integrate will rebuild fresh. The skill's most important step is the learnings write-back at the end, which routes discoveries to stack.md / decisions.md / learnings.jsonl so /integrate can use them without ever reading POC code. Proactively invoke this skill after /scope when the FDE says "let me build a quick thing", "let me try this", "time to prototype", "let's hack something together", or otherwise indicates they're
Code Review
49vitoworleone/claude-code-handbook
Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.
Python Best Practices
43jefflester/claude-skills-supercharged
Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.