Add feature requirements documentation structure

[rradica]

Summary

This PR introduces a standardized documentation structure for feature requirements in the project. It establishes a dedicated Features/ folder with a reusable template and workflow guidelines to ensure consistent feature documentation across the team.

Key Changes

• Added Features/feature-vorlage.md: A comprehensive German-language template for documenting feature requirements, including sections for overview, goals, functional/non-functional requirements, acceptance criteria, and references
• Added Features/README.md: Documentation of the feature documentation workflow, guiding developers on how to use the template and organize feature files
• Updated AGENTS.md: Added a new "Feature requirements" section that references the new documentation structure and explains where and how to document new features

Notable Details

• The template uses a clear, structured format with checkboxes for tracking requirements and acceptance criteria
• Documentation is language-agnostic in structure but uses German labels (reflecting the project's language preference)
• The workflow encourages one feature per Markdown file with descriptive naming conventions
• Integration with the main project README ensures discoverability and adoption of the new documentation standard

https://claude.ai/code/session_01D613xzzyazqaG34uMm4AZu

[gemini-code-assist]

Code Review

This pull request introduces a structured process for documenting feature requirements by adding a new Features/ directory. This directory includes a template (feature-vorlage.md) and a guide (README.md) in German, and AGENTS.md is updated to reference this new workflow. The feedback suggests a minor grammatical correction in the Features/README.md file to maintain consistency by using imperative verbs across all steps.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The list of steps uses imperative verbs for steps 1-3 ('Kopiere', 'Benenne', 'Fülle') but switches to an infinitive verb construction in step 4 ('anlegen'). To maintain grammatical consistency, step 4 should also use the imperative form.

Suggested change

	4. Pro Feature eine eigene MD-Datei anlegen.
	4. Lege pro Feature eine eigene MD-Datei an.