From ccbce7eff195a859f0dc30f36282e84723670a96 Mon Sep 17 00:00:00 2001 From: jarvis-at-skic Date: Tue, 25 Aug 2026 08:18:08 +0000 Subject: [PATCH] feat: include UI UX in channel coordination --- SKILL.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/SKILL.md b/SKILL.md index 830fbce..78ef96e 100644 --- a/SKILL.md +++ b/SKILL.md @@ -14,7 +14,7 @@ metadata: ## Overview -This skill owns release readiness and the controlled release-change workflow for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases` channels for release implications, but it starts release execution only after an explicit team request. +This skill owns release readiness and the controlled release-change workflow for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases` channels for release implications, but it starts release execution only after an explicit team request. Load the global `documentation-docusaurus` skill from `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/documentation-docusaurus` before changing documentation structure, navigation, Markdown/MDX, Docusaurus configuration, or builds. @@ -60,12 +60,13 @@ Inspect only: corp-v1--general corp-v1--scope corp-v1--architecture +corp-v1--ui-ux corp-v1--kanban corp-v1--delivery corp-v1--releases ``` -Use mapped-channel history to avoid duplicate work and new relevant activity from the other five channels. Never inspect another project's channels. +Use mapped-channel history to avoid duplicate work and new relevant activity from the other six channels. Never inspect another project's channels. ## Release Readiness @@ -161,6 +162,10 @@ When separately authorized after approval: Never claim deployment from a merged PR alone. +## UI/UX Coordination + +For frontend-affecting releases, Releases verifies the approved UI/UX acceptance evidence and records production design regressions or user-feedback deltas for the `ui-ux` channel. Release approval and deployment remain owned by Releases. + ## Synchronization Workflow 1. Read new same-project activity and enough release history to avoid duplicates.