ara-cli 0.1.9.69__py3-none-any.whl → 0.1.10.8__py3-none-any.whl

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.

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

@@ -1,13 +0,0 @@
-### COMMANDS FOR AN OBVIOUS IMPLEMENTATION THE INTENDED GOAL
-Your job is now:
-* remember you are strictly following your given RULES AS EXPERT PYTHON DEVELOPER for code and architectural code quality
-* change only code that must changed
-* Implement the code 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
-
-* 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/error_fixing.commands.md

@@ -1,20 +0,0 @@
-### COMMANDS FOR ERROR FIXING
-Your job is now to fix the error:
-* Silently analyze the described error and draft a potential solution to the fix the error
-* Silently review the provided source files to understand both the current faulty implementation and the intended changes to fix the error.
-* 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.

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

@@ -1,18 +0,0 @@
-### COMMANDS FOR UPDATING THE FORMULATION OF FEATURE FILES
-Your job is now:
-* Examine the designated feature file, ensuring it aligns with the content and its relationships within the context files.
-* If there is a discrepancy between the feature's specifications and the system behavior described in the context files, defer to the behavior outlined in the context files. This also applies to behaviors not yet described in the existing feature file.
-* return a table of your five top rated proposed enhancements sorted by the "Formulation enhancement rating" and formatted in the following way (one example line is given as reference):
-| Number | filename | Scenario name | Line of feature file (from - to) | Formulation enhancement rating (0 - 1) | explanation of enhancement | 
-| 1      | file.feature  | some_scenario | 30-65                    | 0.9                             | {here comes an explanation and reasoning of the updated formulation and a reference to the context source} |
-
-* Propose a revised formulation for the feature file based on the analysis.
-* wrap and return the revised formulation in the following format 
-```artefact
-# [ ] extract 
-# filename: {path/artefac_filename.feature} 
-{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 update the formulation of the designated feature file" and then explain what kind of information you think is missing and how I could easily retrieve it  

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

@@ -1,43 +0,0 @@
-### COMMANDS FOR FORMULATING AGILE REQUIREMENTS ARTIFACTS
-Your job is now:
-* remember your RULES
-* 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
-
-* 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      |
-    ```
-
-* wrap and return the formulated feature 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/js_code_generation_simple.commands.md

@@ -1,13 +0,0 @@
-### COMMANDS FOR AN OBVIOUS IMPLEMENTATION THE INTENDED GOAL
-Your job is now:
-* remember you are strictly following your given RULES AS EXPERT JAVASCRIPT DEVELOPER for code and architectural code quality
-* change only code that must changed
-* Implement the code ensuring your generated code blocks are not just code snippets but at complete method levels. Use for every single generated code block this format:
-```js
-# [ ] extract
-# filename: {path/filename}.js
-{js code}
-```
-* 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 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/refactoring.commands.md

@@ -1,15 +0,0 @@
-### COMMANDS FOR REFACTORING
-Your job is now
-* remember you are strictly following your given RULES AS EXPERT PYTHON DEVELOPER
-* analyze again the given files with regard to the intended refactoring
-* refactor to enhance the code as indended
-* return code as fully refactored methods and not as code snippets 
-* return the code in the following format, 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
-
-* 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/refactoring_analysis.commands.md

@@ -1,9 +0,0 @@
-### COMMANDS FOR REFACTORING ANALYSIS
-Your job is now:
-* remember you are strictly following your given RULES AS EXPERT PYTHON DEVELOPER
-* analyze the intended refactoring and make a list of potential code enhancements with regard to the given files
-* return a table of your five top rated proposed enhancements sorted by the "Code enhancement rating" and formatted in the following way (one example line is given as reference):
-| Number | filename | method name | Line of code (from - to) | Code enhancement rating (0 - 1) | explanation of enhancement | 
-| 1      | file.py  | some_method | 30-65                    | 0.9                             | {here comes an explanation that on the level of a precise and detailed refactoring prompt} |
-
-* 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/reverse_engineer_feature_file.commands.md

@@ -1,15 +0,0 @@
-### COMMANDS FOR REVERSE ENGINEER A FEATURE FILE FROM EXISTING CODE
-Your job is now:
-* remember you are strictly following your given RULES AS GHERKIN EXPERT
-* Silently analyze the intended behavior of the given code and if given any other description of the program flow like pseudo code
-* do not add any additional behavior in the feature file, describe strictly the behavior that is defined by code or pseudo code
-* if any existing feature files are provided maximize reusage of formulated steps so that later step implementation effort can be reduces
-
-* return your results in the following format 
-```gherkin
-# [ ] extract
-# filename: {path/filename}.feature
-{feature file}
-```
-
-* in case you think information is missing in order to generate a suffiently precise formulation, return a warning "WARNING: information is missing to correctly fullfill the job!" and then explain what kind of information you think is missing and how I could easily retrieve it.  

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

@@ -1,19 +0,0 @@
-### COMMANDS FOR REVERSE ENGINEER PROGRAM FLOW FROM EXISTING CODE
-Your job is now:
-* remember you are strictly following your given RULES AS CODE ANAYLST
-* Silently analyze the intended behavior of the given code
-* create as result of your silent analysis this analysis table
-  | filename       | method                                   | short description of logical contribution to the logical program flow      |
-  | {filename}.py  | {method name, descriptive name of code block}  | {detailed explanation of the value to the program flow}      |
-
-* then generate based on your analysis and by using your generated analysis table the pseudo code that summarizes the logical flow for the whole process to generate the listing from start to end. Here is an example how the pseude code could look like:
-  ```pseudo code
-Initialize the system to prepare for use
-Verify if the user is authenticated
-IF the user is authenticated:
-    Retrieve and process user information
-ELSE:
-    Display an error message if authentication fails
-  ```
-
-* in case you think information is missing in order to generate a suffiently precise formulation, return a warning "WARNING: information is missing to correctly fullfill the job!" and then explain what kind of information you think is missing and how I could easily retrieve it.  

ara_cli/templates/template.businessgoal

@@ -1,10 +0,0 @@
-@sample_tag
-Businessgoal: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-In order to <reach primarily a monetary business goal>
-As a <business related role>  
-I want <something that helps me to reach my monetary goal>
-
-Description: <further optional description to understand the business goal, markdown capable text formatting>

ara_cli/templates/template.capability

@@ -1,10 +0,0 @@
-@sample_tag
-Capability: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-To be able to <needed capability for stakeholders that are the
-enablers/relevant for reaching the business goal>
-
-Description: <further optional description to understand
-the capability, markdown capable text formatting>

ara_cli/templates/template.epic

@@ -1,15 +0,0 @@
-@sample_tag
-Epic: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-In order to <achieve a benefit>
-As a <(user) role>
-I want <a certain product behavior>
-
-Rule: <rule needed to fulfill the wanted product behavior>
-Rule: <rule needed to fulfill the wanted product behavior>
-Rule: <rule needed to fulfill the wanted product behavior>
-
-Description: <further optional description to understand
-the epic, markdown capable text formatting>

ara_cli/templates/template.example

@@ -1,6 +0,0 @@
-@sample_tag
-Example: <descriptive title>
-
-Illustrates <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-Description: <further optional description to understand the rule, no format defined, the example artefact is only a placeholder>

ara_cli/templates/template.feature

@@ -1,26 +0,0 @@
-@sample_tag
-Feature: <descriptive title>
-
-  As a <user>
-  I want to <do something | need something>
-  So that <I can achieve something>
-
-  Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>   
-
-  Description: <further optional description to understand
-  the rule, no format defined, the example artefact is only a placeholder>
-
-  Scenario: <descriptive scenario title>
-    Given <precondition>
-    When <action>
-    Then <expected result>
-
-  Scenario Outline: <descriptive scenario title>
-    Given <precondition>
-    When <action>
-    Then <expected result>
-
-    Examples:
-      | descriptive scenario title | precondition         | action             | expected result    |
-      | <example title 1>          | <example precond. 1> | <example action 1> | <example result 1> |
-      | <example title 2>          | <example precond. 2> | <example action 2> | <example result 2> |

ara_cli/templates/template.issue

@@ -1,14 +0,0 @@
-@sample_tag
-Issue: <descriptive issue>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>  | blank | filled with text that does not refer to an artefact or rule (then this a free issue)
-
-*Optional descriptions of the issue in Gherkin style*
-
-Given <descriptive text of the starting conditions where the issue occurs>
-When <action under which the issues occurs>
-Then <resulting behavior in contrast to the expected behavior>
-
-*or optional free text description*
-
-Description: <further free text description to understand the issue, no format defined>

ara_cli/templates/template.keyfeature

@@ -1,15 +0,0 @@
-@sample_tag
-Keyfeature: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-In order to <support a capability or business goal>
-As a <main stakeholder who will benefit>
-I want <a product feature that helps me doing something so that I can achieve my named goal>
-
-Description: <further optional description to understand the capability, markdown capable text formatting, best practice is using
-    GIVEN any precondition
-    AND another precondition
-    WHEN some action takes place
-    THEN some result is to be expected
-    AND some other result is to be expected>

ara_cli/templates/template.task

@@ -1,6 +0,0 @@
-@to-do
-Task: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>  | blank | filled with text that does not refer to an artefact or rule (then this is a free task)
-
-Description: <further optional description to understand the task, no format defined>

ara_cli/templates/template.userstory

@@ -1,17 +0,0 @@
-@sample_tag
-Userstory: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-Estimate: <story points, scale?>
-
-In order to <achieve a benefit>
-As a <(user) role>
-I want <a certain product behavior>
-
-Rule: <rule needed to fulfill the wanted product behavior>
-Rule: <rule needed to fulfill the wanted product behavior>
-Rule: <rule needed to fulfill the wanted product behavior>
-
-Description: <further optional description to understand
-the user story, markdown capable text formatting>

ara_cli/templates/template.vision

@@ -1,14 +0,0 @@
-@sample_tag
-Vision: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-For <target customer>
-Who <needs something>
-The <product name> is a <product category>
-That <key benefit, compelling reason to buy>
-Unlike <primary competitive alternative>
-Our product <statement of primary differentiation>
-
-Description: <further optional description to understand
-the vision, markdown capable text formatting>

ara_cli-0.1.9.69.dist-info/METADATA

@@ -1,16 +0,0 @@
-Metadata-Version: 2.4
-Name: ara_cli
-Version: 0.1.9.69
-Requires-Dist: litellm
-Requires-Dist: llama-index
-Requires-Dist: llama-index-llms-openai
-Requires-Dist: llama-index-retrievers-bm25
-Requires-Dist: openai
-Requires-Dist: markdown-it-py
-Requires-Dist: json-repair
-Requires-Dist: argparse
-Requires-Dist: argcomplete
-Requires-Dist: cmd2>=2.5
-Requires-Dist: pydantic
-Requires-Dist: pydantic_ai
-Dynamic: requires-dist