Add tool requirements list

MODULE.bazel

@@ -72,6 +72,6 @@ bazel_dep(name = "rules_java", version = "8.15.1")
 # Score custom modules loading
 #
 ###############################################################################
-bazel_dep(name = "score_tooling", version = "1.1.0")
-bazel_dep(name = "score_docs_as_code", version = "3.0.0")
-bazel_dep(name = "score_process", version = "1.4.3")
+bazel_dep(name = "score_tooling", version = "1.1.2")
+bazel_dep(name = "score_docs_as_code", version = "3.0.1")
+bazel_dep(name = "score_process", version = "1.4.4")

docs/platform_management_plan/problem_resolution.rst

@@ -135,7 +135,7 @@ part of the ISSUE.
 
 To provide solutions, use the Solution part of the ISSUE.
 
-:need:`[[title]] <gd_req__problem_attr_anaylsis_results>` is provided in the analysis
+:need:`[[title]] <gd_req__problem_attr_analysis_results>` is provided in the analysis
 results part of the ISSUE. State here, if the problem is accepted or rejected. Safety/Security
 experts must confirm or deny, if safety/security is affected is set correctly
 

docs/platform_management_plan/security_management.rst

@@ -13,7 +13,7 @@
    # *******************************************************************************
 
 .. document:: Platform Security Plan
-   :id: doc__platform_security_plan
+   :id: doc__score_platform_security_plan
    :status: draft
    :safety: ASIL_B
    :security: YES
@@ -320,7 +320,7 @@ Process status: Status of the workflow which "outputs" the work product, derived
 Security Management Feature Specific Work Products
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-See feature tree documents (created by using :need:`gd_temp__feature_security_wp`):
+See feature tree documents (created by using :need:`doc__feature_name_security_wp`):
 
 <link to document for every feature>
 

docs/score_tools/index.rst

@@ -31,6 +31,7 @@ S-CORE Tools Overview
 
    score_tools_evaluation_list
    tools_documentation/index
+   tools_requirements/index
    tools_static_analysis_code_quality/index
    tools_testing_frameworks/index
    tools_build_development/index

docs/score_tools/tools_requirements/index.rst

@@ -0,0 +1,86 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2026 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+
+Tools Requirements
+==================
+List of all requirements for tools of S-CORE that are not defined or addressed to specific repositories like docs-as-code.
+
+
+.. list-table:: Tool requirements
+    :header-rows: 1
+
+    * - ID
+      - Title
+      - Rationale
+
+    * - :need:`gd_req__doc_author`
+      - Document Author
+      - Author is stored in the PR documentation of GitHub
+
+    * - :need:`gd_req__doc_reviewer`
+      - Document Reviewer
+      - All reviewers can be seen in the PR documentation of GitHub
+
+    * - :need:`gd_req__doc_approver`
+      - Document Approver
+      - Approver can be seen in the PR documentation of GitHub
+
+    * - :need:`gd_req__change_attr_title`
+      - Change Request attribute: title
+      - GitHub issues will be used to create change requests
+
+    * - :need:`gd_req__problem_check_mandatory`
+      - Problem Resolution mandatory attributes provided
+      - GitHub issues will be used to track problems and the mandatory attributes will be provided in the issue template
+
+    * - :need:`gd_req__problem_attr_analysis_results`
+      - Problem Resolution attribute: analysis results
+      - GitHub issues will be used to track problems and analysis results will be provided
+
+    * - :need:`gd_req__problem_attr_classification`
+      - Problem Resolution attribute: classification
+      - GitHub issues will be used to track problems and classification will be provided
+
+    * - :need:`gd_req__problem_attr_impact_description`
+      - Problem Resolution attribute: impact description
+      - GitHub issues will be used to track problems and impact description will be provided
+
+    * - :need:`gd_req__problem_attr_milestone`
+      - Problem Resolution attribute: milestone
+      - GitHub issues will be used to track problems and milestone will be provided
+
+    * - :need:`gd_req__problem_attr_safety_affected`
+      - Problem Resolution attribute: safety affected
+      - GitHub issues will be used to track problems and safety impact will be indicated
+
+    * - :need:`gd_req__problem_attr_security_affected`
+      - Problem Resolution attribute: security affected
+      - GitHub issues will be used to track problems and security impact will be indicated
+
+    * - :need:`gd_req__problem_attr_stakeholder`
+      - Problem Resolution attribute: stakeholder
+      - GitHub issues will be used to track problems and stakeholder information will be provided
+
+    * - :need:`gd_req__problem_attr_status`
+      - Problem Resolution attribute: status
+      - GitHub issues will be used to track problems and status will be maintained
+
+    * - :need:`gd_req__problem_attr_title`
+      - Problem Resolution attribute: title
+      - GitHub issues will be used to track problems and title will be provided
+
+    * - :need:`gd_req__problem_check_closing`
+      - Problem Resolution closing check
+      - GitHub issues will be used to verify all mandatory attributes before closing