legacy-requirements-extractor

Name: legacy-requirements-extractor
Availability: InStock
Author: LLLLimbo

Extract As-Built business requirements from legacy COBOL, Java, SQL, and shell codebases.

Updated Jan 5, 2026

Search Tags:#architecture #requirements #traceability #legacy #code-analysis #reverse-engineering #Horseshoe Model

Ready to run

npx skills add https://github.com/LLLLimbo/Skills --skill legacy-requirements-extractor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legacy-requirements-extractor
Source: https://github.com/LLLLimbo/Skills/tree/main/legacy-requirements-extractor
Command: npx skills add https://github.com/LLLLimbo/Skills --skill legacy-requirements-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Legacy systems encode critical business rules and decisions deep in code, configs, and database logic, making modernization risky and opaque. This Skill applies a formal Requirements Archaeology approach, using the Horseshoe Model to recover the true As-Built requirements and map them to architectural intent.

Core Features & Use Cases

Reconstructs As-Built business requirements from legacy codebases (COBOL, Java, SQL, Shell, and more) by combining static, dynamic, and data-driven analysis.
Generates a Bi-Directional Requirements Traceability Matrix (RTM) that links code artifacts to business rules and supports forward-looking modernization.
Identifies dead code, hidden rules, and configuration-driven policies to guide migration planning and risk assessment.

Quick Start

Analyze the provided legacy repository to produce an RTM and a modeled requirements catalog that supports cloud-native modernization.

Frequently Asked Questions about legacy-requirements-extractor

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

FAQPage Schema

How do I extract business requirements from legacy code for a migration project?▼

Extract business requirements from legacy code by applying Requirements Archaeology and the Horseshoe Model to recover As-Built rules. This process bridges implementation and business intent, producing a traceable requirements list and architecture map to guide modernization.

Can I reverse engineer COBOL and Java codebases to generate a requirements traceability matrix?▼

Yes, you can reverse engineer COBOL and Java codebases to generate a Bi-Directional Requirements Traceability Matrix (RTM). The analysis links code artifacts directly to business rules, supporting forward-looking cloud-native migration planning.

What is the Horseshoe Model in legacy code analysis?▼

The Horseshoe Model in legacy code analysis is a formal Requirements Archaeology approach used to recover true As-Built requirements. It maps deep implementation logic in code, configs, and database artifacts to architectural intent and business decisions.

Does this approach work with SQL and shell scripts or only COBOL?▼

This approach works with SQL and shell scripts, as well as COBOL and Java artifacts. It combines static, dynamic, and data-driven analysis across these formats to identify hidden rules and configuration-driven policies.

How do I identify dead code and hidden business rules before modernizing a legacy system?▼

Identify dead code and hidden business rules by analyzing legacy codebases to extract As-Built requirements. This process reveals configuration-driven policies and opaque logic, enabling accurate risk assessment and migration strategy planning.

When should I not use reverse engineering for legacy modernization?▼

You should reconsider reverse engineering for legacy modernization if your codebase lacks clear static artifacts or configuration files to analyze. The approach relies on accessing these implementation details to successfully map architectural intent and business rules.