ara-cli 0.1.10.5__py3-none-any.whl → 0.1.11.0__py3-none-any.whl

ara_cli/templates/prompt-modules/commands/python_bug_fixing_code.commands.md

@@ -0,0 +1,34 @@
+### COMMANDS FOR FIXING BUGS
+
+Your job is now to fix the described error:
+
+* Silently analyze the given error description or error log files
+* Silently review the provided source files and if given the provided feature file (specified behavior) to understand the current faulty implementation and draft silently a potential solution to fix the error
+* Develop implementation strategies that minimize code changes, prefer reusing existing methods over new implementations. Also always prefer to use existing python packages over your own implementation.
+
+When you touch code or need to generate code for bug fixing:
+* The max function or method length should not exceed 40 lines.
+* The max class length should not exceed 150 lines.
+* The max file length should not exceed 150 lines.
+* Split implementation files or functions/methods/classes in case they exceed their defined length maximum.
+* Apply as coding and design principle the separation of concerns and single responsibility principle in general and specifically when you need to split.
+
+* Important: you are NOT allowed to do any further refactorings not related to the bug fixing implementation. Refactoring for enhancing the code quality is not allowed.
+* The fixed code must fully implement the specified behavior in an easy testable and modular/extensible way.
+* Follow PEP8 coding guidelines.
+* Use descriptive numpy style docstrings for inline method and class documentation.
+* Use the python logger logging package to implement logging for all application modules that enables a fine granular full observability of the program flow by the log file. Use ./logs/<module_name>.log as filepath for logging.
+
+* Only return full copy pastable file content.
+* Use for every single generated code block this markdown code block format:
+
+```python
+# [ ] extract
+# filename: src/{filename}.py
+{python code}
+```
+
+* The extract and filename statements are only allowed once per code block
+* The first character of the first line inside your code block must be '#' and the first character of the second line inside your code block must be '#'
+* replace the '# [ ] extract' statement of the template with '# [x] extract' in your response
+* in case of files get deprecated give me a list of files that can be safely deleted

ara_cli/templates/prompt-modules/commands/python_generate_code.commands.md

@@ -0,0 +1,27 @@
+### COMMANDS FOR IMPLEMENTING ONE OR A SET OF NEW OR CHANGED FEATURE FILES
+
+Your job is now:
+* Silently analyze the given feature files and the specified behavior.
+* Develop implementation strategies that minimize code changes with respect to any given code and test files, prefer reusing existing methods over new implementations.
+* The max function length should not exceed 25 lines. The max file length should not exceed 120 lines.
+* Always prefer to use existing python packages over your own implementation.
+* In case additional implementation instructions are given as:
+  * Specified in files with extensions "*.technology.md" follow strictly the specified mandatory python packages and tech stack
+  * Explicitly specified as example reference implementation: use this reference information as starting point for your own implementation
+* Fully implement the specified behavior in an easy testable and modular/extensible way, fully implement unit tests for your production code (try to achieve at least 90% code coverage) and implement for all given feature files the corresponding step definitions. Follow PEP8 coding guidelines, use numpy style docstrings for inline function documentation, apply as coding and design principle the separation of concerns and single responsibility principle.
+* Generated or reworked python methods must not exceed 25 lines of code. In case methods exceed this length they need to be split according to the single responsibility principle and separation of concerns.
+* Generated or reworked python files must not exceed 120 lines of code. In case files exceed this length they need to be split according to the single responsibility principle and separation of concerns.
+* Use the python logger logging package to implement logging for all application modules that enable a full observability of the program flow over the log file. Use ./logs/<module_name>.log as filepath for logging.
+
+* Only return full copy pastable file content for production code, unit test files and step definition files. Use for every single generated code block this markdown code block format:
+
+```python
+# [ ] extract
+# filename: src/{filename}.py
+{python code}
+```
+
+* The extract and filename statements are only allowed once per markdown code block
+* The first character of the first line inside your code block must be '#' and the first character of the second line inside your code block must be '#'
+* replace the '# [ ] extract' statement of the template with '# [x] extract' in your response
+* in case of files get deprecated give me a list of files that can be safely deleted

ara_cli/templates/prompt-modules/commands/python_refactoring_code.commands.md

@@ -0,0 +1,39 @@
+### COMMANDS FOR REFACTORING
+
+Your job is now to refactor the code for enhancing the code quality and the design of the code according to the following guidelines:
+* Refactoring = Changing the internal structure of code
+* Without changing its external behavior
+* Goal = Improve readability, maintainability, and design
+-> "Refactoring is a change made to the internal structure of software to make it easier to understand and cheaper to modify without changing its observable behavior."
+-> "Refactoring changes how code is written, not what it does."
+
+Now do:
+* Silently analyze the given code base
+* Silently analyze the given feature file (specified behavior) to fully understand the flow and logic of the current implementation. Remember: you are not allowed to change specified behavior.
+
+When you refactor the code remember:
+* The max function or method length should not exceed 40 lines.
+* The max class length should not exceed 150 lines.
+* The max file length should not exceed 150 lines.
+* Split implementation files or functions/methods/classes in case they exceed their defined length maximum.
+* Apply as coding and design principle the separation of concerns and single responsibility principle in general and specifically when you need to split.
+* Flatten nested code structures (e.g. if/while/for statements) to only one nesting level.
+* The refactored code must fully implement the specified behavior in an easy testable and modular/extensible way.
+* Follow PEP8 coding guidelines.
+* Use descriptive numpy style docstrings for inline method and class documentation.
+* Use the python logger logging package to implement logging for all application modules that enables a fine granular full observability of the program flow by the log file. Use ./logs/<module_name>.log as filepath for logging.
+
+Your output specification is:
+* Only return full copy pastable file content.
+* Use for every single generated code block this markdown code block format:
+
+```python
+# [ ] extract
+# filename: src/{filename}.py
+{python code}
+```
+
+* The extract and filename statements are only allowed once per markdown code block
+* The first character of the first line inside your code block must be '#' and the first character of the second line inside your code block must be '#'
+* replace the '# [ ] extract' statement of the template with '# [x] extract' in your response
+* in case of files get deprecated give me a list of files that can be safely deleted

ara_cli/templates/prompt-modules/commands/python_step_definitions_generation_and_fixing.commands.md

@@ -0,0 +1,40 @@
+### COMMANDS FOR CREATING AND CORRECTING STEP DEFINITIONS FOR FEATURE FILES
+
+**MANDATORY INPUT VALIDATION:**
+- Feature files (.feature) must be provided
+- Behave test report must be provided
+
+**PROMPT DEFINITION ERROR:** If mandatory input is missing, immediately stop and return: "ERROR: Missing mandatory input. Please provide both feature files (.feature) and behave test report before proceeding."
+
+**OPTIONAL INPUT:**
+- Already existing step definitions
+
+**PROMPT DEFINITION WARNING:** If optional input is missing: "WARNING: No existing step definitions provided. If step definitions already exist in your project, please include them as input context to avoid duplication and ensure consistency."
+
+### Your job is now:
+* Silently analyze the given feature files and behave test report to understand current test failures and missing step implementations.
+* Silently review any provided existing step definitions to avoid duplication and maintain consistency.
+* Develop step definition implementation strategies that minimize code changes with respect to existing step definitions, prefer reusing existing step patterns over new implementations.
+* The max function length should not exceed 25 lines. The max file length should not exceed 120 lines.
+* Always prefer to use existing python packages over your own implementation.
+* Use the behave testing framework for all step definition implementations.
+* Apply mocking extensively to isolate step definitions from external inputs and interfaces using unittest.mock or pytest-mock.
+* Fully implement all missing step definitions for the given feature files in an easy testable and modular/extensible way. Follow PEP8 coding guidelines, use numpy style docstrings for inline function documentation, apply as coding and design principle the separation of concerns and single responsibility principle.
+* Generated or reworked python methods must not exceed 25 lines of code. In case methods exceed this length they need to be split according to the single responsibility principle and separation of concerns.
+* Generated or reworked python files must not exceed 120 lines of code. In case files exceed this length they need to be split according to the single responsibility principle and separation of concerns.
+* Implement proper assertion methods that provide clear error messages when steps fail.
+* Use context.scenario, context.feature, and context.table appropriately for data sharing between steps.
+* Implement proper cleanup in @after_scenario and @after_feature hooks when necessary.
+
+* Only return full copy pastable file content for step definition files. Use for every single generated code block this markdown code block format:
+
+```python
+# [ ] extract
+# filename: ara/features/steps/{filename}_steps.py
+{python code}
+```
+
+* The extract and filename statements are only allowed once per markdown code block
+* The first character of the first line inside your code block must be '#' and the first character of the second line inside your code block must be '#'
+* replace the '# [ ] extract' statement of the template with '# [x] extract' in your response
+* in case of files get deprecated give me a list of files that can be safely deleted

ara_cli/templates/prompt-modules/commands/python_unittest_generation_and_fixing.commands.md

@@ -0,0 +1,48 @@
+### COMMANDS FOR CREATING AND CORRECTING UNIT TESTS
+
+**MANDATORY INPUT VALIDATION:**
+- Feature files (.feature) must be provided
+- Code coverage report or pytest test report must be provided
+
+**PROMPT DEFINITION ERROR:** If mandatory input is missing, immediately stop and return: "ERROR: Missing mandatory input. Please provide both feature files (.feature) and code coverage/pytest test report before proceeding."
+
+**OPTIONAL INPUT:**
+- Already existing unit tests
+
+**PROMPT DEFINITION WARNING:** If optional input is missing: "WARNING: No existing unit tests provided. If unit tests already exist in your project, please include them as input context to avoid duplication and ensure consistency."
+
+#### Your job is now:
+* Silently analyze the given feature files and code coverage/pytest test report to understand current test gaps and implementation requirements.
+* Silently review any provided existing unit tests to avoid duplication and maintain consistency with existing test patterns.
+* Develop unit test implementation strategies that minimize code changes with respect to existing tests, prefer reusing existing test patterns and fixtures over new implementations.
+* The max function length should not exceed 25 lines. The max file length should not exceed 120 lines.
+* Always prefer to use existing python packages over your own implementation.
+* Use the pytest testing framework for all unit test implementations.
+* Apply mocking extensively to isolate unit tests from external inputs and interfaces using unittest.mock or pytest-mock. Mock all external dependencies, file I/O, network calls, and database interactions.
+* Fully implement comprehensive unit tests that achieve at least 90% code coverage for the specified behavior in an easy maintainable and modular/extensible way. Follow PEP8 coding guidelines, use numpy style docstrings for inline function documentation, apply as coding and design principle the separation of concerns and single responsibility principle.
+* Generated or reworked python methods must not exceed 25 lines of code. In case methods exceed this length they need to be split according to the single responsibility principle and separation of concerns.
+* Generated or reworked python files must not exceed 120 lines of code. In case files exceed this length they need to be split according to the single responsibility principle and separation of concerns.
+
+* Implement comprehensive test cases covering:
+  - Happy path scenarios
+  - Edge cases and boundary conditions
+  - Error handling and exception scenarios
+  - Input validation scenarios
+
+* Use pytest fixtures for test data setup and teardown to ensure test isolation.
+* Implement parametrized tests using @pytest.mark.parametrize for testing multiple input combinations efficiently.
+* Use descriptive test method names that clearly indicate what is being tested.
+* Include proper assertions with meaningful error messages.
+
+* Only return full copy pastable file content for unit test files. Use for every single generated code block this markdown code block format:
+
+```python
+# [ ] extract
+# filename: test/test_{filename}.py
+{python code}
+```
+
+* The extract and filename statements are only allowed once per markdown code block
+* The first character of the first line inside your code block must be '#' and the first character of the second line inside your code block must be '#'
+* replace the '# [ ] extract' statement of the template with '# [x] extract' in your response
+* in case of files get deprecated give me a list of files that can be safely deleted

ara_cli/version.py

@@ -1,2 +1,2 @@
 # version.py
-__version__ = "0.1.10.5"   # fith parameter like .0 for local install test purposes only. official numbers should be 4 digit numbers
+__version__ = "0.1.11.0"   # fith parameter like .0 for local install test purposes only. official numbers should be 4 digit numbers

{ara_cli-0.1.10.5.dist-info → ara_cli-0.1.11.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ara_cli
-Version: 0.1.10.5
+Version: 0.1.11.0
 Summary: Powerful, open source command-line tool for managing, structuring and automating software development artifacts in line with Business-Driven Development (BDD) and AI-assisted processes
 Description-Content-Type: text/markdown
 Requires-Dist: langfuse
@@ -20,6 +20,7 @@ Requires-Dist: pydantic_ai
 Requires-Dist: python-docx
 Requires-Dist: pymupdf4llm
 Requires-Dist: typer
+Requires-Dist: psutil
 Dynamic: description
 Dynamic: description-content-type
 Dynamic: requires-dist
@@ -130,6 +131,35 @@ ara autofix
 
 See `ara -h` for the complete list of commands and usage examples.
 
+---
+## Agent Commands
+
+`ara-cli` includes powerful agent-based capabilities that can be accessed through the interactive chat. These agents can perform complex, multi-step tasks, such as conducting interviews or automating coding workflows.
+
+To use the agent commands, first start an interactive chat session:
+
+```bash
+ara prompt chat <artefact_classifier> <artefact_name>
+```
+
+Once inside the chat, you can use the following commands to manage agents:
+
+| Command          | Shortcut | Description                                       |
+| ---------------- | -------- | ------------------------------------------------- |
+| `AGENT_RUN`      | `a`      | Run an agent by name.                             |
+| `AGENT_STOP`     | `as`     | Stop the currently running agent.                 |
+| `AGENT_CONTINUE` | `ac`     | Continue the agent's operation without new input. |
+| `AGENT_STATUS`   | `astat`  | Show the status of the current agent.             |
+| `exit`           |          | Exit from agent interfacto back to chat.          |
+
+**Example:**
+
+```bash
+ara> a interview_agent
+```
+
+**Important:** The agent functionality requires the `ara-agents` package to be installed separately. If you do not have `ara-agents` installed, please contact the Talsen Team for assistance.
+
 ---
 
 ## Artefact Structure

{ara_cli-0.1.10.5.dist-info → ara_cli-0.1.11.0.dist-info}/RECORD

@@ -1,5 +1,5 @@
-ara_cli/__init__.py,sha256=DuzXKimZ6JtUEnp48qCQcnojDflBtYjT6Na_twO5EzM,505
-ara_cli/__main__.py,sha256=wtPH57qlVQVIJ1vC-W_B3JIReJvvsstfouaOA7NY-zA,12569
+ara_cli/__init__.py,sha256=w_BYefMe7IdHoAycBTn0VxHr686Ha9oCCVnO5eWjeTU,504
+ara_cli/__main__.py,sha256=mT5ljAyzjYtWFcuO7DR455f9QLZHpWtDfN0Cpw4kwHA,11411
 ara_cli/ara_command_action.py,sha256=yWtZXxwGp-n5kl-I6bMvwESfyRVGHHBYHVapu-8knl4,24618
 ara_cli/ara_config.py,sha256=vZsY2zYJdlSExRE84L5LqRH3DjveeuMSmG5fC8HDIVc,9794
 ara_cli/artefact_autofix.py,sha256=wLAWKGjhNqXZjsBqy98L3ZpDzg8S5OzFeroJBxGyAAw,26308
@@ -11,13 +11,13 @@ ara_cli/artefact_lister.py,sha256=M-ggazAgZ-OLeW9NB48r_sd6zPx0p4hEpeS63qHwI1A,41
 ara_cli/artefact_reader.py,sha256=-6E1VhIlh2oJE1Rn8ARcHRc_E9N4uk8cEViKMoywm6E,7753
 ara_cli/artefact_renamer.py,sha256=8S4QWD19_FGKsKlWojnu_RUOxx0u9rmLugydM4s4VDc,4219
 ara_cli/artefact_scan.py,sha256=qY2Gp4zVcqMXhtuP7rICW0UBG4pcj3W2ABofnL9SIG8,4806
-ara_cli/chat.py,sha256=II3lnzuCWDnjTSWTO-XbhTgY3EoEbFimcRHg9wQjKq4,40270
+ara_cli/chat.py,sha256=_1xjUPuBWFxeXQ-9QDf1pJe5x7Xr9lEaSkeQMrCTpYg,44337
 ara_cli/classifier.py,sha256=zWskj7rBYdqYBGjksBm46iTgVU5IIf2PZsJr4qeiwVU,1878
 ara_cli/codefusionretriever.py,sha256=fCHgXdIBRzkVAnapX-KI2NQ44XbrrF4tEQmn5J6clUI,1980
 ara_cli/codehierachieretriever.py,sha256=Xd3EgEWWhkSf1TmTWtf8X5_YvyE_4B66nRrqarwSiTU,1182
 ara_cli/commandline_completer.py,sha256=b00Dqb5n7SecpxYIDLxAfYhp8X6e3c8a5qYz6ko0i3E,1192
 ara_cli/completers.py,sha256=V4bcmUnuFkdgMpJ3bLAL7cnxinxZb8wwB17WnRHIrHM,5404
-ara_cli/directory_navigator.py,sha256=6QbSAjJrJ5a6Lutol9J4HFgVDMiAQ672ny9TATrh04U,3318
+ara_cli/directory_navigator.py,sha256=mr34qhuz8MT2Qj_sTddffCB2nzYpWCg9AWLPdaFjeOM,4518
 ara_cli/error_handler.py,sha256=nNaJSq82f3xiz_QFRKPg5kX_-oI-UoFdRJ2OTj1AR18,4019
 ara_cli/file_classifier.py,sha256=nUcNrhflUydCyCRbXHjEEXYwwwfUm65lYnNEvc86fpM,4026
 ara_cli/file_lister.py,sha256=0C-j8IzajXo5qlvnuy5WFfe43ALwJ-0JFh2K6Xx2ccw,2332
@@ -34,7 +34,7 @@ ara_cli/tag_extractor.py,sha256=vjuPGGlT3mQpez6eY9LLgIBFQqPsTEgfAWODbXlgODc,4057
 ara_cli/template_loader.py,sha256=nYQ4zadcXX6oXSNgFNlXx8u5961BZCj3dw0tSKHdNfE,10756
 ara_cli/template_manager.py,sha256=l2c785YHB7m0e2TjE0CX-nwXrS4v3EiT9qrS5KuatAc,7105
 ara_cli/update_config_prompt.py,sha256=moqj2Kha7S7fEGzTReU0v2y8UjXC8QfnoiieOQr35C4,5157
-ara_cli/version.py,sha256=Hwkja5NG6SdOg-ccF1I4uuSp_0zOE28sIV9RMXv82EI,146
+ara_cli/version.py,sha256=A7GCqR2NtmlH854O1ujcswyBm-a8O6nrMFHIv3aoNHQ,146
 ara_cli/ara_subcommands/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 ara_cli/ara_subcommands/autofix.py,sha256=h7-6hV97Q6PisUJ_U1Qs4sHYwkHsDpeYH63y_LQsfSc,1095
 ara_cli/ara_subcommands/chat.py,sha256=9zorWKbM0ulu9xFhW2tzV5vl8hCLOCjcp2E9hYgZJ90,1239
@@ -74,6 +74,11 @@ ara_cli/artefact_models/serialize_helper.py,sha256=Wks30wy-UrwJURetydKykLgJkdGRg
 ara_cli/artefact_models/task_artefact_model.py,sha256=1BSMbz9D-RXvdpdd0RlAr9hUx84Rcuysk2YfQC8Qy14,6046
 ara_cli/artefact_models/userstory_artefact_model.py,sha256=P5an9UrZ1QrQ57TxSJ48F2OwKxhqEz1B-QxTtHeSZFI,7172
 ara_cli/artefact_models/vision_artefact_model.py,sha256=frjaUJj-mmIlVHEhzAQztCGs-CtvNu_odSborgztfzo,5251
+ara_cli/chat_agent/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+ara_cli/chat_agent/agent_communicator.py,sha256=Tru2o7LZ0n2iQ1ip01ZFt5d9iwAI6Pcgj6NBK5OF1_A,2349
+ara_cli/chat_agent/agent_process_manager.py,sha256=k_AfG1pr2xbhDVSUm79r5RnOKpdzCvTS3VpUpgIvHUA,7349
+ara_cli/chat_agent/agent_status_manager.py,sha256=CflNgTKjF6MnyiU_5u97LUfpUw9vvAdDm71xFROSupY,2337
+ara_cli/chat_agent/agent_workspace_manager.py,sha256=2Oj8GP6qpme9kTI0Ele3H9VNJr2O6VpuHE8-nsy3LRE,2683
 ara_cli/commands/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 ara_cli/commands/command.py,sha256=Y_2dNeuxRjbyI3ScXNv55lptSe8Hs_ya78L0nPYNZHA,154
 ara_cli/commands/extract_command.py,sha256=CzUOwDembG587PYbxg5rge4XSfdsuTyOPUvkobkXCIs,573
@@ -102,30 +107,24 @@ ara_cli/templates/template.steps.prompt_log.md,sha256=sd8g1KtwgpPvU-vGWAFCDXiWHk
 ara_cli/templates/template.task.prompt_log.md,sha256=4kAy1zC0k3_y3SoYb-mg3rQEJCW_c43X7ggOLZ321TE,190
 ara_cli/templates/template.userstory.prompt_log.md,sha256=Yp62iF7zDy2XNIwwJN35jKKSmezinK_JKbSvVuagtmA,205
 ara_cli/templates/template.vision.prompt_log.md,sha256=CAzBzj3O23CzrPIUq3xzpXGKn3_nAvyBLRUi-5Bnq_0,196
-ara_cli/templates/prompt-modules/blueprints/complete_pytest_unittest.blueprint.md,sha256=DtZsdfVDNy9_cGE_Nn_TE2T3oRwr27kecZchOp5uIG0,672
 ara_cli/templates/prompt-modules/blueprints/empty.blueprint.md,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-ara_cli/templates/prompt-modules/blueprints/pytest_unittest_prompt.blueprint.md,sha256=4R6Vtr55ZaPkOYM6K8_4vkHX91n5pZ1_CAVez-k9Cws,1305
 ara_cli/templates/prompt-modules/blueprints/task_todo_list_C4_architecture_analysis.blueprint.md,sha256=jEZrZaVK_pkRhLp1SpTX3xR6BGXkox6NafXEjX_GDvM,3099
-ara_cli/templates/prompt-modules/blueprints/task_todo_list_implement_feature_BDD_way.blueprint.md,sha256=EimfgzjhFIsZnJ0qMNbVlUQEU0vC9Sv1VupesLz7A1E,2088
 ara_cli/templates/prompt-modules/commands/architecture_C4_analysis.commands.md,sha256=xzfmOBsETlh90P1haJOiC8y8eLPboZ3yFodbuSUPLBU,1557
 ara_cli/templates/prompt-modules/commands/architecture_radon_cc_score.commands.md,sha256=t-cozhSQPGUOoYfdySBL4n-yQykvCc4s5n0AKpKCn0Q,3074
 ara_cli/templates/prompt-modules/commands/architecture_radon_halstead_v.commands.md,sha256=YBQKZdTJ4QRnBocsWTvT9dmaHOKys1hE0NJC7LPl2vQ,1676
 ara_cli/templates/prompt-modules/commands/architecture_radon_maintainability_score.commands.md,sha256=9nBsY_EYNI9GmD-KzbGKdtEDP4YoY7ECV2QWEzoznfc,5511
-ara_cli/templates/prompt-modules/commands/artefact_classification.commands.md,sha256=6qA0v-1_GYtI2UNIg1kzkidCOpLj1YqkeSL6PpvfK5Q,829
-ara_cli/templates/prompt-modules/commands/artefact_extension.commands.md,sha256=9nN3nZ9wl5eabtb1VrhH3qUsEC4kTD5yoc_woMejqd0,1060
-ara_cli/templates/prompt-modules/commands/artefact_formulation.commands.md,sha256=kB4mmVGraMuquqlWkC51Fqw9fara3U-82ldJlSBG3k0,797
-ara_cli/templates/prompt-modules/commands/behave_step_generation.commands.md,sha256=18Zzw_rhBY5Lyx_PrIUEGiidSLNCIgIUucUUQHVXFdo,4240
-ara_cli/templates/prompt-modules/commands/code_generation_complex.commands.md,sha256=gQE4JoXkEFWh9YyQBMrLjljT9WoGljRfpdFtUIbT4lw,1413
-ara_cli/templates/prompt-modules/commands/code_generation_simple.commands.md,sha256=_PX0Q108bgNqnxz4VKSkuaU2OiHS9eRMqXH2kO9d0E4,836
-ara_cli/templates/prompt-modules/commands/empty.commands.md,sha256=XynQO_CPitumyZ9ky6AvqeE00Kl5A3-VDa1MOoChd8c,807
-ara_cli/templates/prompt-modules/commands/error_fixing.commands.md,sha256=HaWY8djKQRB-CfCGVEndczBYsg_OSXnE6vDU7_LaU2o,1425
-ara_cli/templates/prompt-modules/commands/feature_file_update.commands.md,sha256=NEv95oef4p5H0qUjMkLnu1ljRGV0q4-lNUL1NAJbI-0,1611
-ara_cli/templates/prompt-modules/commands/feature_formulation.commands.md,sha256=8D9LfJYqUKBh-TKc-WFJT6v4m69VgKZAhplYysro29U,1754
-ara_cli/templates/prompt-modules/commands/js_code_generation_simple.commands.md,sha256=_j_gONkhJDXE5TUPTpyYlF45uZ4MSZG1LnoHlndnRGY,832
-ara_cli/templates/prompt-modules/commands/refactoring.commands.md,sha256=3I4df3oeGOrGPqnu_IvDSQNzNscYK1VbEpFxu8DwGrQ,932
-ara_cli/templates/prompt-modules/commands/refactoring_analysis.commands.md,sha256=RjMAa6rBCou0XGhu1-IFGy21EgcxSUkGWSCCqbw6CFw,1028
-ara_cli/templates/prompt-modules/commands/reverse_engineer_feature_file.commands.md,sha256=9togxxeBTcSvD5hLdBqyC-rUCF-xhU68PtD5rQySbFY,964
-ara_cli/templates/prompt-modules/commands/reverse_engineer_program_flow.commands.md,sha256=-pW71nV064aTfLTyYEnkH5eAaZPH3HRdOQsSxAfiNu8,1315
+ara_cli/templates/prompt-modules/commands/empty.commands.md,sha256=vgi8-ep2JZBuv0cocpBWJe1-gDzpw1OpHt5KANtaH58,80
+ara_cli/templates/prompt-modules/commands/extract_general.commands.md,sha256=g21jnK5gd0UX8dLv8IpxOX-r5A61EpVgT1VcmxXPcTw,718
+ara_cli/templates/prompt-modules/commands/extract_markdown.commands.md,sha256=em3jFTXNzT5ULdOyFg__DlRciYOTuCXrHiImnJS5B4M,657
+ara_cli/templates/prompt-modules/commands/extract_python.commands.md,sha256=BhTtbfnrr_ABHza0XmGYlQ8YzrESQumyobQj2Ff9dNM,641
+ara_cli/templates/prompt-modules/commands/feature_add_or_modifiy_specified_behavior.commands.md,sha256=vuGfxSifR1UGxUhOQakEYA2KkoK66s_jf2pn6ClHuM0,2444
+ara_cli/templates/prompt-modules/commands/feature_generate_initial_specified_bevahior.commands.md,sha256=oufTleuQcHiYmdzKTtDleMHHN6anw-n8JSpUKUzE7GQ,2810
+ara_cli/templates/prompt-modules/commands/prompt_template_tech_stack_transformer.commands.md,sha256=Z32V1Ux94Uol3gqxqV8V6gdiKSIyrbtd6re7tuLIRsM,4446
+ara_cli/templates/prompt-modules/commands/python_bug_fixing_code.commands.md,sha256=slOySzxZnIXzmIma3jZVvGcNC-llkqlhUil1cuWYE2U,2273
+ara_cli/templates/prompt-modules/commands/python_generate_code.commands.md,sha256=LYNfVuAhtBHB1CDjUqy5Y6dDmq9PVfo8UbJbfB2_mKE,2601
+ara_cli/templates/prompt-modules/commands/python_refactoring_code.commands.md,sha256=p-Y1r10-80Eo7lUmz2hX7uJto8J2-d2C0RMV595t0Sg,2453
+ara_cli/templates/prompt-modules/commands/python_step_definitions_generation_and_fixing.commands.md,sha256=i74lgqMc9KFu9QWfOcZR1jcDMLAZCW4wvGvGRK7Yng0,3204
+ara_cli/templates/prompt-modules/commands/python_unittest_generation_and_fixing.commands.md,sha256=jMuMfOiw_H8RL-I8J5OqBO4rpzYmGgGgzh-kKt_fNkg,3561
 ara_cli/templates/prompt-modules/intentions/classify_task.intention.md,sha256=9ZiEOBFiku24SX4kBJlSCgm5ScYlNZIcNPoHwtGbWIU,254
 ara_cli/templates/prompt-modules/intentions/empty.intention.md,sha256=6dqUtORC992KagZX2Up2yHHvBjVgDTj--wIyYbG4jhc,48
 ara_cli/templates/prompt-modules/intentions/error_fixing.intention.md,sha256=pcfG4csCF830lk8anDCkOA0ewTYnRo5mg0Y0w-fyEJU,206
@@ -187,8 +186,8 @@ tests/test_tag_extractor.py,sha256=7eVD10Y1uLkoSrEgqkXzRvPFs8lJ1RiaJzDu7ml_FZE,3
 tests/test_template_loader.py,sha256=R7s8HJZbKqja-1TRBMBkVKPTgajofUjjRKUJq7a3_Oc,7427
 tests/test_template_manager.py,sha256=qliEeYgAEakn8JIqIHa8u0Ht6DY4L3T6DcHBXkjzR4I,4167
 tests/test_update_config_prompt.py,sha256=xsqj1WTn4BsG5Q2t-sNPfu7EoMURFcS-hfb5VSXUnJc,6765
-ara_cli-0.1.10.5.dist-info/METADATA,sha256=bif1qapBgIms0mokosJMv63sWZe-eVp5pQepUA5h5HM,6834
-ara_cli-0.1.10.5.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-ara_cli-0.1.10.5.dist-info/entry_points.txt,sha256=v4h7MzysTgSIDYfEo3oj4Kz_8lzsRa3hq-KJHEcLVX8,45
-ara_cli-0.1.10.5.dist-info/top_level.txt,sha256=WM4cLHT5DYUaWzLtRj-gu3yVNFpGQ6lLRI3FMmC-38I,14
-ara_cli-0.1.10.5.dist-info/RECORD,,
+ara_cli-0.1.11.0.dist-info/METADATA,sha256=J3UhEy0Gi12HQIjRZlfq9raSlOLt5NDpk2qZLwNUdx0,8141
+ara_cli-0.1.11.0.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+ara_cli-0.1.11.0.dist-info/entry_points.txt,sha256=v4h7MzysTgSIDYfEo3oj4Kz_8lzsRa3hq-KJHEcLVX8,45
+ara_cli-0.1.11.0.dist-info/top_level.txt,sha256=WM4cLHT5DYUaWzLtRj-gu3yVNFpGQ6lLRI3FMmC-38I,14
+ara_cli-0.1.11.0.dist-info/RECORD,,

ara_cli/templates/prompt-modules/blueprints/complete_pytest_unittest.blueprint.md

@@ -1,27 +0,0 @@
-# Usage: 
-# necessary input and adaption: 
-# replace text snippets in <> with specific context
-# ...
-# expected output: 
-# ...
-Do not use usage information as prompt instructions
-
-
-Given source code
-```python
-<source code for context, skip irrelevant for current task>
-```
-
-Given existing unit tests
-```python
-<existing unit tests>
-```
-
-Given pytest is available
-
-Modify and/or create unit tests so this is fully covered:
-```python
-<snippet you want to cover in the next step>
-```
-
-Give me only what is relevant to testing this snippet. Use parametrization where applicable. Split into multiple tests instead of using if-else blocks. Mock all dependencies of tested code.

ara_cli/templates/prompt-modules/blueprints/pytest_unittest_prompt.blueprint.md

@@ -1,32 +0,0 @@
-MODE: STRICT_GENERATION
-TASK: Produce one complete pytest file for a given Python module.
-
-REQUIREMENTS:
-- Output only valid Python code (no text, no markdown).
-- Target: full behavioral + branch coverage (100%).
-- Tests follow AAA pattern (# Arrange, # Act, # Assert).
-- Exactly ONE assert or ONE pytest.raises() per test.
-- Use tmp_path fixture for filesystem isolation.
-- Include an autouse=True fixture for global patching if needed.
-- No external I/O or network calls.
-- All tests independent, self-contained.
-
-STYLE:
-- File starts with module docstring describing AAA, single assert rule, autouse fixture.
-- Group tests with comment headers: 
-  # --- Success paths --- / # --- Error paths --- / # --- Edge cases ---
-- Function names: test_<function>_<expected_behavior>_<condition>
-- Variables descriptive (rel, path, new_content, etc.).
-- Use direct asserts (assert result is True, assert path.read_text() == "x").
-- For errors: 
-  with pytest.raises(ExceptionType, match=r"text"): function_call()
-
-COVERAGE:
-- Include success, failure, and rare edge branches (e.g., conditional exceptions).
-- Ensure 100% of conditional branches executed.
-
-OUTPUT:
-- Single .py file, runnable via: pytest -v --disable-warnings --maxfail=1 --cov=<target_module>
-- No explanations or prose, only the test code.
-
-END

ara_cli/templates/prompt-modules/blueprints/task_todo_list_implement_feature_BDD_way.blueprint.md

@@ -1,30 +0,0 @@
-### INTENTION and CONTEXT
-My intention is to setup a todo list in my given task that helps me to implement a feature in a BDD way
-
-Now do the following:
-Search for a line starting with `Task: ` defined in the `### GIVENS` section. Just repeat the task_name you have found as confirmation
-* Do not proceed if no task is defined. Return immediatly with the message: "No task defined as prompt control" 
-
-* Focus on the description in the `Description` section of the defined task. Ignore all other sections.
-* Analyze the content of the task description section and adapt your default recipe accordingly. You can add new "[@to-do]s ...", you can delete "[@to-do]s" that are not necessary anymore according to the existing task description content
-
-* the format and formulation of your default recipe implementing a feature in BDD style is
-```
-[@to-do] analyze and understand the given `user story`
-[@to-do] generate an example contributing to the rule `rule of userstory to implement` which should be turned into a scenario or feature description
-[@to-do] use the example and aditional relevant context `{context list}` to formulate the feature file
-[@to-do] use the formulated feature file, relevant existing step implementations and relevant existing production code to implement the new step implementations that will fail
-[@to-do] use the created step definitions, the relevant existing production code to modify existing code and to create new code implementing the requested behavior so that the step implementations will pass 
-```
-
-* append your recipe at the end of task
-* return the extended task in the following format 
-```artefact
-# [ ] extract 
-# filename: ara/tasks/{task_name}.task 
-{initial task content}
-{recipe}
-```
-* the extract and filename statements are only allowed once per code block
-
-* in case you think information is missing in order to generate a suffiently precise formulation, return a warning "WARNING: information is missing to formulate the new artefacts" and then explain what kind of information you think is missing and how I could easily retrieve it  

ara_cli/templates/prompt-modules/commands/artefact_classification.commands.md

@@ -1,9 +0,0 @@
-### COMMANDS FOR THE CORRECT CONTEXTUAL CLASSIFICATION OF ARTIFACTS
-Your job is now:
-* analyze the given files with respect to content and relationship
-* analyze the new artefact with respect to content and the relationship to the given files
-* give me a list of the top 5 artefacts to which the new artefact contributes the most
-* the output format must be a table with the columns
-  | artefact name | contribution rating from 0 (very low) - 1 (very high) | arguments for rating | path to artefact |
-
-* in case you think the relationship of the new artefact is to weak to any given files, return a warning "WARNING: new artefact is not directly related to already existing aretefacts" and then make a proposal with regard of the ara "work orchestration contribution hierarchy" and/or the "specification contribution hierarchy" 

ara_cli/templates/prompt-modules/commands/artefact_extension.commands.md

@@ -1,17 +0,0 @@
-### COMMANDS FOR EXTENDING EXISTING AGILE REQUIREMENTS ARTIFACTS
-Your job is now:
-* analyze the given files with respect to content and relationship
-* analyze the new or changed behavior with respect to content and the relationship to the existing artefacts
-* Develop formulation strategies that minimize formulation changes of existing changes.
-* generate a formulation proposal that adds the new context and or behavior for the specified documents
-* wrap and return the formulated  in the following format 
-```artefact
-# [ ] extract 
-# filename: {path/filename.filextension} 
-{formulation}
-```
-* the extract and filename statements are only allowed once per code block
-
-* Adhere strictly to established rules for AGILE PRODUCT OWNERS for high-quality specification artefacts.
-
-* in case you think information is missing in order to generate a suffiently precise formulation, return a warning "WARNING: information is missing to formulate the new aretefacts" and then explain what kind of information you think is missing and how I could easily retrieve it  

ara_cli/templates/prompt-modules/commands/artefact_formulation.commands.md

@@ -1,14 +0,0 @@
-### COMMANDS FOR FORMULATING AGILE REQUIREMENTS ARTIFACTS
-Your job is now:
-* analyze the given files with respect to content and relationship
-* analyze the new artefact with respect to content and the relationship to the given files
-* generate a formulation proposal for the specified documents
-* wrap and return the formulated  in the following format 
-```artefact
-# [ ] extract 
-# filename: {path/filename.filextension} 
-{formulation}
-```
-* the extract and filename statements are only allowed once per code block
-
-* in case you think information is missing in order to generate a suffiently precise formulation, return a warning "WARNING: information is missing to formulate the new artefacts" and then explain what kind of information you think is missing and how I could easily retrieve it  

ara_cli/templates/prompt-modules/commands/behave_step_generation.commands.md

@@ -1,102 +0,0 @@
-### COMMANDS FOR IMPLEMENTING A STEP IMPLEMENTATION FROM A GIVEN FEATURE FILE
-Your job is now:
-* Silently analyze the given feature file to understand the required step implementations.
-* Silently review any additionally provided source files to check if any reusable step implementations already exist or if the necessary support methods are available.
-* Develop implementation strategies that minimize code changes, prefer reusing existing methods and step definitions over new implementations. 
-* Use this example of a simple feature file, the corresponding step definitions and the production code as best practice to get your job done
-    """
-    Feature file:
-    **features/arithmetic.feature**
-    ```gherkin
-    Feature: Arithmetic Operations
-
-    Contributes to: <Any artefact name to which this feature contributes value> <Classifier of this artefact>
-
-      Scenario: Addition of two numbers
-        Given the CLI is initialized
-        When the user runs the addition command with "2" and "3"
-        Then the result should be "5"
-
-      Scenario Outline: Subtraction of two numbers
-        Given the CLI is initialized
-        When the user runs the subtraction command with "<num1>" and "<num2>"
-        Then the result should be "<result>"
-
-        Examples:
-          | num1 | num2 | result |
-          | 5    | 3    | 2      |
-          | 10   | 4    | 6      |
-          | 0    | 0    | 0      |
-    ```
-
-    Step Definitions in Python with behave as BDD test framework:
-    **features/steps/arithmetic_steps.py**
-    ```python
-    import subprocess
-    from behave import given, when, then
-
-    @given('the CLI is initialized')
-    def step_given_cli_initialized(context):
-        context.cli_command = 'python path/to/your_arithmetic_script.py'
-
-    @when('the user runs the addition command with "{num1}" and "{num2}"')
-    def step_when_user_runs_addition_command(context, num1, num2):
-        context.result = subprocess.run(
-            [context.cli_command, 'add', num1, num2],
-            capture_output=True,
-            text=True
-        ).stdout.strip()
-
-    @when('the user runs the subtraction command with "{num1}" and "{num2}"')
-    def step_when_user_runs_subtraction_command(context, num1, num2):
-        context.result = subprocess.run(
-            [context.cli_command, 'subtract', num1, num2],
-            capture_output=True,
-            text=True
-        ).stdout.strip()
-
-    @then('the result should be "{expected_result}"')
-    def step_then_result_should_be(context, expected_result):
-        assert context.result == expected_result, f"Expected {expected_result} but got {context.result}"
-    ```
-
-    CLI Script as example production code to satisfiy the interfaces defined in the step definitions (DO NOT GENERATE ANY PRODUCTION CODE NOW):
-    **your_arithmetic_script.py**
-    ```python
-    import sys
-
-    def add(a, b):
-        return int(a) + int(b)
-
-    def subtract(a, b):
-        return int(a) - int(b)
-
-    if __name__ == "__main__":
-        if len(sys.argv) != 4:
-            print("Usage: python your_arithmetic_script.py <operation> <num1> <num2>")
-            sys.exit(1)
-
-        operation = sys.argv[1]
-        num1 = sys.argv[2]
-        num2 = sys.argv[3]
-
-        if operation == 'add':
-            print(add(num1, num2))
-        elif operation == 'subtract':
-            print(subtract(num1, num2))
-        else:
-            print(f"Unknown operation: {operation}")
-            sys.exit(1)
-    ```
-    """ 
-* Systematically search and check if any of the new step definitions is already existing in any given step file. It must then be omitted in the new step definitions generation. Otherwise it will create an ambiguous steps error in the behave registry.    
-* return the generated step definitions in this format:
-```python
-# [ ] extract
-# filename: {path/filename}.py
-{python code}
-```
-
-* The extract and filename statements are only allowed once per code block.
-* Adhere strictly to established rules for high-quality Python code and architecture.
-* If essential information is missing for code generation, issue a warning: "WARNING: Information is missing to do a correct step implementation." Specify what information is lacking and suggest how it might be retrieved.

ara_cli/templates/prompt-modules/commands/code_generation_complex.commands.md

@@ -1,20 +0,0 @@
-### COMMANDS FOR IMPLEMENTING THE INTENDED GOAL
-Your job is now:
-* Silently analyze the intended behavior and draft potential new implementations in pseudo code.
-* Silently review the provided source files to understand both the current behavior and the intended new implementation.
-* Develop implementation strategies that minimize code changes, prefer reusing existing methods over new implementations.
-* Output a "change table" listing all necessary changes. Include an example line for reference:
-  | filename       | method                                   | short description of intended changes      |
-  | {filename}.py  | {method name of existing or new method}  | {detailed explanation of the changes serving as code generation prompt}      |
-
-* Implement the changes as specified in the change table, ensuring your generated code blocks are not just code snippets but at complete method levels. Use for every single generated code block this format:
-```python
-# [ ] extract
-# filename: {path/filename}.py
-{python code}
-```
-* the extract and filename statements are only allowed once per code block
-
-* Adhere strictly to established rules for high-quality Python code and architecture.
-
-* If essential information is missing for code generation, issue a warning: "WARNING: Information is missing to do a correct implementation." Specify what information is lacking and suggest how it might be retrieved.