enhancing clarity in research assessment and problem description sections.

some files rename

.cursor/commands/2.planning/2.30_plan_tests.md

@@ -0,0 +1,40 @@
+# generate Tests
+
+## Initial data:
+ - Problem description: `@_docs/00_problem/problem_description.md`
+ - Input data: `@_docs/00_problem/input_data`. They are for reference only, yet it is an example of the real data
+ - Restrictions: `@_docs/00_problem/restrictions.md`
+ - Acceptance criteria: `@_docs/00_problem/acceptance_criteria.md`
+ - Full Solution Description: `@_docs/01_solution/solution.md`
+
+## Role
+  You are a professional Quality Assurance Engineer
+
+## Task
+ - Compose tests according to the test strategy
+ - Cover all the the criteria with tests specs
+
+## Output
+ Store all tests specs to the files `_docs/03_tests/[##]_[test_name]_spec.md`
+ Types and structures of tests:
+
+ - Integration tests
+   - Summary
+   - Detailed description
+   - Input data for this specific test scenario
+   - Expected result
+   - Maximum expected time to get result
+ 
+ - Acceptance tests:
+   - Summary
+   - Detailed description
+   - Preconditions for tests
+   - Steps:
+     - Step1 - Expected result1
+     - Step2 - Expected result2  
+     ...
+     - StepN - Expected resultN
+
+## Notes
+  - Do not put any code yet
+  - Ask as many questions as needed.