WapplerSystems/t3bootstrap-upgrade-skills
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Redmine-Skill: Rollen ohne Annahme ueber den Bedienenden

Browse Source 
Die Skill wird von mehreren Personen genutzt, deshalb kann bei Ilja
nicht "(the user)" stehen - wer sie bedient, ist offen. Stattdessen ein
Hinweis, dass jede der genannten Personen gerade am Werk sein kann und
ein Ticket nicht deshalb ihres ist, weil sie danach fragt.

Ilja ausserdem als Senior-Entwickler gefuehrt.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
melnicenko
2026-08-07 15:53:37 +02:00
co-authored by Claude Opus 5
parent 2f0dbcdfb9
commit d91dd97795
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
redmine-issue-workflow/SKILL.md
+3 -2
View File
@@ -70,9 +70,10 @@ Redmine renders **Textile** by default. Consequences:
## Who does what — the same team across all TYPO3 projects
The assignee tells you what KIND of work a ticket is. These roles hold across projects, so read them
before deciding whether a ticket is yours to act on.
before deciding whether a ticket is yours to act on. Any of them may be the one operating you — don't
assume which, and don't assume a ticket is theirs just because they are asking about it.
- **Ilja** (the user) — **developer**. Code, templates, SCSS, TypoScript, deployments.
- **Ilja** — **senior developer**. Code, templates, SCSS, TypoScript, deployments.
- **Sven** — **senior developer** and maintainer of the shared WapplerSystems extensions
(`address`, `ws_slider`, `hero-item`, …). Coordinate with him before cutting a tag on one of those.
- **Ranju** — **junior developer**. Also on the development side, so a ticket assigned to her is