Revert "Merge remote-tracking branch 'origin/main' into feat-spec-approach"

This reverts commit 4850677, reversing
changes made to 3a2ff65.

Author: jkordick

.github/copilot-instructions.md

@@ -0,0 +1,31 @@
+<!-- Use this file to provide workspace-specific custom instructions to Copilot. For more details, visit https://code.visualstudio.com/docs/copilot/copilot-customization#_use-a-githubcopilotinstructionsmd-file -->
+
+# COBOL to Java Quarkus Migration Project
+
+This project is a C# Semantic Kernel application that migrates COBOL code to Java Quarkus. The key components are:
+
+1. **Agents**: AI-powered agents for COBOL analysis and Java conversion
+2. **Process Framework**: Orchestrates the migration workflow
+3. **Models**: Data structures for COBOL and Java code
+
+## Development Guidelines
+
+- Follow C# and .NET coding conventions
+- Use XML documentation comments for public members
+- Use async/await for asynchronous operations
+- Handle exceptions appropriately
+- Log important events and errors
+
+## Key Classes
+
+- **CobolAnalyzerAgent**: Analyzes COBOL code structure
+- **JavaConverterAgent**: Converts COBOL to Java Quarkus
+- **MigrationProcess**: Orchestrates the workflow
+- **FileHelper**: Manages file operations
+
+## Technologies
+
+- Microsoft Semantic Kernel
+- .NET 8.0
+- System.CommandLine
+- OpenAI API integration

.github/prompts/3rd-party.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+Identify code segments that could be removed by using a modern 3rd-party dependency or library. Document these findings in a markdown file. Be precise.

.github/prompts/comments.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+If information in the code is unclear or ambiguous, add clarifying comments. Be precise. Focus on the essentials.

.github/prompts/deterministic.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+Identify recurring deterministic structures and patterns in the codebase. Document these findings in a markdown-file to aid in understanding the code's behavior and to inform potential refactoring efforts. Be precise.

.github/prompts/flow-analysis.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+Use or generate a call chain and visualize it in a mermaid diagram.

.github/prompts/remove-information.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+Look at the code and identify potential comments or information that are not relevant to the current implementation. Remove any unnecessary comments, documentation, or code snippets that do not contribute to the understanding or functionality of the code. Stay precise. When in doubt, keep the information or comment.

.github/prompts/reverse-engineering.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+Extract the business logic of the cobol files, include technical documentation, comments and user handbooks (if they exist). Write all your findings into a markdown file. Be thorough and ensure that all relevant information is captured but stay precise.

.github/prompts/testing.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+If test files exist, have a look at them and understand the testing strategy and applied testing techniques. Document your findings in a markdown file. If no tests exist, generate a strategy how you would cover the code with tests. Be precise.

.github/prompts/translate.prompt.md

@@ -0,0 +1,4 @@
+---
+mode: agent
+---
+If code or comments are not in English: translate the comments to English. For variables, functions, methods, add a comment in English explaining their purpose. Be precise.

Agents/BusinessLogicExtractorAgent.cs

@@ -89,7 +89,11 @@ public async Task<BusinessLogic> ExtractBusinessLogicAsync(CobolFile cobolFile,
                 };
             }
 
-            var systemPrompt = PromptLoader.LoadSection("BusinessLogicExtractor", "System");
+            var systemPrompt = @"
+You are a business analyst extracting business logic from COBOL code.
+Focus on identifying business use cases, operations, and validation rules.
+Use business-friendly terminology from the provided glossary when available.
+";
 
             // Build glossary context
             var glossaryContext = "";
@@ -103,12 +107,56 @@ public async Task<BusinessLogic> ExtractBusinessLogicAsync(CobolFile cobolFile,
                 glossaryContext += "\n";
             }
 
-            var userPrompt = PromptLoader.LoadSection("BusinessLogicExtractor", "User", new Dictionary<string, string>
-            {
-                ["GlossaryContext"] = glossaryContext,
-                ["FileName"] = cobolFile.FileName,
-                ["CobolContent"] = contentToAnalyze
-            });
+            var userPrompt = $@"
+Analyze this COBOL program and extract the business logic:
+Your goal: Identify WHAT the business does, not HOW the code works.{glossaryContext}
+
+## What to Extract:
+
+### 1. Use Cases / Operations
+Identify each business operation the program performs:
+- CREATE / Register / Add operations
+- UPDATE / Change / Modify operations  
+- DELETE / Remove operations
+- READ / Query / Fetch operations
+- VALIDATE / Check operations
+
+### 2. Validations as Business Rules
+Extract ALL validation rules including:
+- Field validations (required, format, length, range)
+- Business logic validations
+- Error codes and their meanings
+
+### 3. Business Purpose
+What business problem does this solve? (1-2 sentences)
+
+## Format Your Response:
+
+## Business Purpose
+[1-2 sentences]
+
+## Use Cases
+### Use Case 1: [Operation Name]
+**Trigger:** [What initiates this operation]
+**Description:** [What happens]
+**Key Steps:**
+1. [Step 1]
+2. [Step 2]
+
+## Business Rules & Validations
+### Data Validations
+- [Field name] must be [requirement] - Error: [code/message]
+
+### Business Logic Rules
+- [Rule description]
+
+File: {cobolFile.FileName}
+
+COBOL Code:
+```cobol
+{contentToAnalyze}
+```
+";
 
             var (analysisText, usedFallback, fallbackReason) = await ExecuteWithFallbackAsync(
                 systemPrompt,