From e57e8b5b3e1350feeb2a5a18133f9779bdcc072e 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 | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/SKILL.md b/SKILL.md index a419528..1b66f98 100644 --- a/SKILL.md +++ b/SKILL.md @@ -1,7 +1,7 @@ --- name: corp-v1-channel-delivery description: "Use when operating or synchronizing a Corp v1 project's delivery channel. Drives coding, unit testing, build and continuous-integration health, attempts safe evidence-based fixes, escalates requirement or architecture contradictions, and maintains Ways of Working and Engineering documentation." -version: 1.5.0 +version: 1.5.1 author: Hermes Agent license: MIT metadata: @@ -14,7 +14,7 @@ metadata: ## Overview -This skill owns delivery health for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases` channels and implements only tasks whose parent Feature has explicit human `Approved for Implementation` evidence and which a human team member separately admitted to Kanban Focus `InBacklog`. +This skill owns delivery health for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases` channels and implements only tasks whose parent Feature has explicit human `Approved for Implementation` evidence and which a human team member separately admitted to Kanban Focus `InBacklog`. Its scope includes coding, unit testing, builds, continuous integration, review readiness, delivery blockers, and maintenance of the project documentation's `Ways of Working` and `Engineering` areas. @@ -56,12 +56,13 @@ Every delivery iteration must complete at least one useful, safe activity for an ## Approved Information Boundary -Inspect only the project's six channels: +Inspect only the project's seven channels: ```text corp-v1--general corp-v1--scope corp-v1--architecture +corp-v1--ui-ux corp-v1--kanban corp-v1--delivery corp-v1--releases @@ -148,6 +149,10 @@ Maintain two documentation areas. Update these pages from verified project practice. Do not document a planned process as already operational. +## UI/UX Coordination + +For frontend-affecting work, Delivery requires the approved UI/UX design package, exact Penpot links, responsive/state behavior, accessibility criteria, and mapped tasks. Delivery reports implementation deviations to UI/UX with concrete evidence rather than silently changing the approved experience. + ## Synchronization Workflow 1. Read new same-project activity and enough delivery history to avoid duplicates.