23 KiB
name, description, version, author, license, metadata
| name | description | version | author | license | metadata | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| channel-delivery-skic | 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. | 1.15.0 | Hermes Agent | MIT |
|
SKIC Delivery Channel Reference
Overview
Hermes Kanban direct-link contract
Whenever a response mentions a Hermes Kanban board, initiative, card, or task, it must include a direct dashboard link in the form [descriptive board label](<dashboard-public-url>/kanban?board=<board-slug>). Resolve the dashboard public URL and exact board slug before reporting; never provide only a board name, slug, card count, “visible cards,” or “available in the dashboard.” If no task-specific deep link exists, link the board and include the exact task ID or title in the same statement. Project-adopted skills must replace this generic form with their verified project board URL.
Canonical Scope Status Vocabulary
Before reporting or changing lifecycle status, load status-and-reporting.md and read the project's current Ways of Working Scope page. That contract retains the complete canonical vocabulary, requested wave format and gate codes; development-integrity owns checkpoint claims. Delivery claims only an exact READY_FOR_DELIVERY Task into IN_PROGRESS, without a second Focus admission. BLOCKED remains a separate flag; merge/green CI is not DONE, and releasable application work normally ends Delivery at TO_BE_RELEASED.
This skill owns delivery health for a Corp v1 project. It monitors the project's general, scope, architecture, ui-ux, kanban, delivery, uat, and releases channels and implements only tasks whose parent Feature has explicit human Approved for Implementation evidence and whose exact Task status is READY_FOR_DELIVERY. That status is the Focus-admitted pickup handoff; no separate post-status admission gate exists.
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.
Delivery owns application unit testing only plus static/build-time validation of the application artifacts it publishes: Dockerfiles, image/container contracts, publication records/workflows, and Helm chart linting/rendering/packaging. The project's standalone E2E repository under its UAT channel owns every functional non-unit suite and its fixtures, configuration, runner, and evidence: integration, browser, E2E, acceptance, security-boundary, performance, runtime-budget, smoke, regression, and deployed-environment testing. Delivery must not maintain or execute functional non-unit suites in the application repository. E2E must not install Helm or build/publish application images. It consumes UAT failures as defect evidence, fixes application code with unit-first TTD, and hands the corrected deployed tuple back to UAT.
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.
Load the global corp-v1-glossary skill from https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-glossary whenever project documentation needs to define or explain a reusable term. Maintain one canonical definition in the project's final top-level Glossary area and link to it from the owning domain page; do not duplicate glossary-style explanations across channel documentation.
Shared Corp v1 System Login
Before login, load channel-board-skic from its authoritative source and follow Corp v1 System SSO Credential Use in full. It owns origin/purpose verification, runtime-only HL_V1_SSO_EMAIL / HL_V1_SSO_PASSWORD handling, non-disclosure, missing-secret injection and session safety. If that policy cannot be loaded, stop before login. Secret availability is not authorization; Delivery grants no account recovery, credential/MFA, permission, billing, destructive-operation or unrelated-access authority.
When to Use
Use this skill when:
- operating in
<code>-delivery; - running its recurring synchronization job;
- implementing or reviewing project code;
- adding or repairing unit tests only; non-unit coverage is routed to the project's UAT channel and standalone E2E repository;
- diagnosing build or CI failures;
- checking implementation against requirements and ADRs;
- maintaining delivery-oriented documentation.
Do not use it to silently choose between contradictory requirements or architecture decisions, approve releases, or bypass review and branch protections.
Development Skill Routing
This channel skill owns delivery governance and project-channel coordination. Reusable engineering procedures belong to the global development-* skills below; load the matching skill before the action and treat a project-adopted variant as the project-specific overlay when one exists.
| Work | Required reusable skill | Authoritative Gitea source |
|---|---|---|
| dependency-wave claim, continuation, recovery, and closure | development-durable-wave-execution |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-durable-wave-execution |
| immutable candidate review, exact-head CI, merge, and integration gates | development-gates |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-gates |
| delivery, CI, blocker, and completion reporting | development-integrity |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-integrity |
| behavior changes, defect fixes, and refactoring | development-method-ttd |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-method-ttd |
| branch naming, worktrees, PR topology, and base synchronization | development-branching-strategy |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-branching-strategy |
| pnpm/TypeScript monorepo implementation | development-monorepo-pnpm |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-monorepo-pnpm |
Taskfile, .scripts/, shell wrappers, environment validation, and Devbox |
development-scripts |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-scripts |
| Gondor Argo CD template, rendered desired state, and repository connection | development-gitops-argo-cd-home-gondor-v1 |
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/development-gitops-argo-cd-gondor-v1 |
The channel skill may narrow authority, lifecycle, workspace, visibility, handoff, and evidence requirements. When a project/channel overlay conflicts with a reusable skill on branch naming, human confirmation, worker count, review identity, merge authority, deployment authority, or release authority, the explicit project/channel overlay wins; inherit only the non-conflicting mechanics. It must not restate generic RED–GREEN–REFACTOR mechanics, shell-module layouts, pnpm workspace conventions, ordinary Git branching mechanics, exact-head gate algorithms, or Argo CD authoring procedures. Improve those reusable skills at their linked sources and keep only the project/channel overlay here.
Implementation Entry Gate
Before starting or continuing Feature implementation, verify in project documentation:
- Feature ID and parent Epic;
- explicit human
Approved for Implementationevidence; - linked FRs/NFRs and accepted solution/ADR context;
- task breakdown and dependencies;
- target version and status;
- acceptance evidence expected from delivery.
- exact Task
READY_FOR_DELIVERYevidence, which itself records human Kanban Focus admission.
Hermes cannot approve a Feature for implementation or move a Task to READY_FOR_DELIVERY. Once that exact state exists, Hermes must not require a second Focus-admission decision; Delivery claims the Task by moving it to IN_PROGRESS.
Immediate Wave-Start Visibility Gate
Load development-durable-wave-execution, development-branching-strategy, and development-gates before claiming or starting a wave. Those skills own durable whole-wave claims, branch/worktree mechanics, immutable candidate identity, and exact-head review/CI behavior.
The Corp v1 overlay is narrower: every Task requires a dedicated visible branch and PR before substantive coding, and that PR must carry the Task ID, wave, planned scope, current state, exact head, and governed test base. If Gitea requires a delta, use an empty kickoff commit rather than a filler file. Read the branch and PR back before editing. One Task maps to one branch and PR unless Architecture or the human owner explicitly approves another topology.
Proactive Iteration Requirement
Every delivery iteration must complete at least one useful, safe activity for an implementation-approved Feature or delivery-health need: implement an unblocked task, add unit tests, diagnose/fix CI, improve build tooling, update real Ways of Working/Engineering guidance, verify dependency readiness, or document a concrete blocker with evidence. Never create filler changes. Select work only from exact Tasks in READY_FOR_DELIVERY; claiming one moves it to IN_PROGRESS. Keep architecture's approved task/dependency plan and project documentation current.
Approved Information Boundary
Inspect only the project's eight channels:
<code>-general
<code>-scope
<code>-architecture
<code>-ui-ux
<code>-kanban
<code>-delivery
<code>-uat
<code>-releases
Use enough delivery history to avoid duplicate work and only relevant new activity from the other channels. Never inspect another project.
Delivery Responsibilities
Coding
Load the project-adopted engineering skill for the repository stack before editing. development-monorepo-pnpm owns pnpm/TypeScript workspace implementation, while development-scripts owns Taskfile, .scripts/, shell-wrapper, environment-validation, and Devbox conventions. Delivery adds only the approved requirement/Task boundary, traceability, and prohibition on unrelated refactoring or fabricated evidence.
Unit testing
Load development-method-ttd for every behavior change, defect fix, or refactor. It owns RED–GREEN–REFACTOR mechanics, focused-test progression, and test-design anti-patterns. Delivery requires unit tests to map to approved acceptance evidence and retains their real commands/results. UAT owns every functional non-unit test required to prove that evidence outside the unit boundary; Delivery retains build-time image/container/Helm artifact validation.
Build and continuous integration
Load development-gates before candidate review, remote CI, merge, or integration validation, and load development-integrity before reporting their status. These skills own exact-head identity, attempt integrity, base-drift handling, candidate-versus-integration separation, and honest checkpoint wording.
Delivery still monitors repository-specific compile/type, unit-test, lint/format, dependency, packaging, workflow, image/container contract, Helm chart, and artifact-publication failures. Functional non-unit browser, integration, performance, security-boundary, and acceptance failures arrive as UAT evidence and are routed back for application remediation. A green local build is never remote CI evidence.
Per-project reusable CI base images
Each project should own corp-v1-<code>/corp-v1-<code>-base-images when stable runtimes or OS tools would otherwise be downloaded repeatedly in CI. Before creating, publishing or consuming an image, load the project base-image bindings and required owner loads. It retains digest pinning, credential-free candidate validation, trusted integration-branch publication, immutable tags/digest readback, fail-closed tests and forward repair with the last known-good digest. Runtime smoke remains UAT-owned; reusable mechanics are owned by devsecops-ci-cd-gitea through that decision-point reference.
Runtime-resource placement
CI jobs and developer workstations must not provision databases, queues, object stores, caches, brokers, or other application runtime services. When implementation or validation needs such a resource, provision it under the owning application on the approved shared runtime platform through that project's GitOps repository, then consume it through a governed application or test interface.
- Keep every non-production environment—including development, integration, test, staging, and preview—and all of its resources isolated from production and from other non-production environments. Destructive or concurrent validation requires a per-run database/schema/role or explicit serialization; it must not reset shared data.
- CI may orchestrate exact-head validation, but it must not start application runtime-resource service containers or receive application-resource credentials. Harmless process-local test doubles and build tools are not runtime resources. Prefer a narrowly governed in-platform Job/Workflow trigger so a private resource does not need public, NodePort, or runner-network exposure.
- Persistent storage must follow the project's named platform storage operations skill; load that skill before designing or mutating storage. If the project instead names an approved storage procedure, read that exact procedure and verify its current provenance before acting. If neither an approved skill nor an approved procedure is identified, stop and route the missing decision to Architecture/platform operations; do not infer a provider or provisioning method. Never accept a dynamically provisioned volume whose reclaim policy can delete durable data when the PVC is removed.
- Secrets come from the approved external secret store; never commit connection strings or credentials.
- Provision and verify required runtime resources before treating dependent application work as deployable. Missing infrastructure blocks deployment, not safe code-only work whose tests do not require that resource.
Failure-Repair Workflow
Load failure-and-documentation.md when a build or CI failure is observed. It owns diagnosis, safe forward repair, affected validation, exact-head CI and escalation destinations. Keep repairable failures in the same Task/gate; pause only for the documented external, authority, decision or safety blocker. Never guess requirements or Architecture, weaken a gate or treat a blocker as passing.
Documentation Ownership
Delivery owns verified Ways of Working and Engineering content, not documentation-platform mechanics. Before changing either area, load the domain coverage contract, the linked global documentation-docusaurus source and the project-adopted documentation overlay. Load corp-v1-glossary before defining reusable terms. Keep planned practice distinct from operational evidence.
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
- Read new same-project activity and enough delivery history to avoid duplicates.
- Verify human
Approved for Implementationevidence, exact TaskREADY_FOR_DELIVERYstate, task dependencies, and target version before task work. - Identify executable tasks, CI failures, blockers, requirements/ADR implications, and documentation drift.
- Load all applicable project engineering skills.
- Complete at least one useful safe activity when an authorized path exists; otherwise document and route the exact blocker.
- Escalate uncertainty or contradiction rather than selecting direction.
- Verify local and remote results and update task/Feature progress in project documentation.
- Maintain Ways of Working and Engineering pages when durable practice changed.
- Post a concise update with work completed, evidence, blockers, and required decisions.
Authority and Escalation
May autonomously:
- run unit tests, builds, Delivery artifact validations, and read-only checks; functional non-unit suites run through UAT;
- repair clear CI/build defects within authorized scope;
- add unit tests for an approved behavior and request non-unit coverage from UAT;
- maintain accurate delivery documentation;
- prepare branches/commits/PRs where the project workflow authorizes it.
Requires approval before:
- changing requirements or architecture to make tests pass;
- merging protected changes;
- deploying or releasing;
- changing secrets, permissions, costs, external services, or destructive resources;
- suppressing required quality/security gates.
Evidence Requirements
Include repository, branch, commit SHA, changed paths, commands, local results, CI run/task IDs and status, and relevant requirement/ADR references. Report blockers honestly.
Mined Project-Adoption Improvements
Review provenance and exclusions: AeroSim lessons review.
Dedicated Project Channel Workspace
Every project adoption must bind this channel to a dedicated local workspace under the active working root. Keep clones, worktrees, plans, reports, screenshots, generated artifacts, retained logs, and channel inputs inside that channel root. Use run-unique or task-specific children under workspace/; keep durable project truth in approved repositories. A local folder boundary organizes execution only—it neither broadens authority nor replaces remote evidence. Delivery adoptions should additionally use a channel-level cache/ for reusable pinned toolchains and dependencies, while keeping Task evidence isolated by Task.
Project-Adoption Delivery Lessons
Use the exact Task-file state. The canonical progression is IN_BACKLOG → READY_FOR_DELIVERY → IN_PROGRESS → TO_BE_RELEASED → DONE; BLOCKED is a separate reasoned flag, and neither merge nor green CI means DONE. A Task already in READY_FOR_DELIVERY is Focus-admitted and pickup-ready; Delivery claims it by moving directly to IN_PROGRESS without inventing a second admission gate.
Keep exactly one Task active unless the adopted project authority explicitly defines another safe model. Establish a visible branch and PR before implementation, freeze Task/branch/PR identity, verify every review against the exact candidate head, and end Delivery ownership at TO_BE_RELEASED. Failed gates remain active and are repaired forward until they pass or a genuine external, authority, decision, or safety blocker is evidenced.
Load the matching detailed reference at the decision point—not from memory:
- Task selection, execution, review, merge, and handoff: references/task-delivery-gates.md
- Status, wave, blocker, CI, and completion wording: references/status-and-reporting.md
- Workspace, branch, PR, and visibility entry: references/repository-entry-and-visibility.md
- Toolchain contexts, CI, images, and runtime placement: references/runtime-and-ci.md
- Failure repair and Delivery-owned documentation: references/failure-and-documentation.md
- Planning-artifact reconciliation: references/planning-artifact-reconciliation.md
- Gate failures, resumptions, blockers, merge, and completion: references/common-pitfalls.md
Project adoptions may narrow execution to a named main session or prohibit subagents/cron. Preserve that project-local authority overlay; the central reference does not grant account recovery, permission changes, merge, release, or deployment authority.
When selectable controls are needed, explain every complete option and its trade-offs in prose first, then use short Option A, Option B, and so on labels in the control. Put the recommended option first and keep button labels free of hidden consequences.
Common Pitfalls
Load common-pitfalls.md on failed gates, resumed work and before blocker/CI/merge/completion reports. It retains the complete Delivery traps, including approval/admission, same-project scope, useful safe activity, real evidence and same-gate forward repair. These reminders do not replace the ordered Task gates.
Verification Checklist
- Only same-project channels and repositories were used.
- Work maps to approved requirements/architecture.
- Feature has explicit human
Approved for Implementationevidence and a documented target version. - Selected tasks respect documented dependencies and carry exact Task
READY_FOR_DELIVERYevidence. - At least one useful delivery activity was completed, or a concrete blocker was documented and routed.
- Applicable project skills were loaded.
- Tests and builds were actually run.
- Remote branch and matching CI head SHA were verified.
- Contradictions were escalated, not guessed through.
- Ways of Working and Engineering documentation remains accurate.
- Completed work includes exact evidence.
Canonical naming and compatibility
- Canonical installed and repository name:
channel-delivery-skic. - Source:
https://gitea.lego-cloud.eu/home-v1-skills-code-agent/channel-delivery-skic. - Previous name:
corp-v1-channel-delivery; retained locally only as a compatibility alias. New guidance and presentations use the canonical name. - Naming-only migration authorized by RootAtSkic in presentation message 1562523679223578705. Repository ID, history, support files, project authority and organization ownership are preserved.
- This is a reusable central reference, not a new shared Discord channel. Project adoptions use
channel-delivery-skic-<code>and remain separately owned. - Current project channel:
<code>-deliveryinsideskic-<code>.