home-v1-skills-code-agent/corp-v1-channel-delivery
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request 'feat: include UI/UX in Corp v1 channel coordination' (#1) from feat/ui-ux-channel-sync into test

Browse Source
This commit was merged in pull request #1.
This commit is contained in:
jarvis-at-skic
2026-08-25 01:18:38 -07:00
parent e822da66b8 e57e8b5b3e
commit b629921b6f
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+8 -3
View File
@@ -1,7 +1,7 @@
--- ---
name: corp-v1-channel-delivery 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." 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 author: Hermes Agent
license: MIT license: MIT
metadata: metadata:
@@ -14,7 +14,7 @@ metadata:
## Overview ## 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. 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 ## Approved Information Boundary
Inspect only the project's six channels: Inspect only the project's seven channels:
```text ```text
corp-v1-<code>-general corp-v1-<code>-general
corp-v1-<code>-scope corp-v1-<code>-scope
corp-v1-<code>-architecture corp-v1-<code>-architecture
corp-v1-<code>-ui-ux
corp-v1-<code>-kanban corp-v1-<code>-kanban
corp-v1-<code>-delivery corp-v1-<code>-delivery
corp-v1-<code>-releases corp-v1-<code>-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. 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 ## Synchronization Workflow
1. Read new same-project activity and enough delivery history to avoid duplicates. 1. Read new same-project activity and enough delivery history to avoid duplicates.