feat: establish channel reference skill scaffold

2026-08-13 11:05:16 +00:00
commit a3b2b956a6
1 changed files with 50 additions and 0 deletions
@@ -0,0 +1,50 @@
+---
+name: corp-v1-channel-delivery
+description: "Use as the central reference when defining or adopting project-scoped operating guidance for a Corp v1 delivery channel. This repository is initial setup only; detailed purpose and procedures remain pending steering walkthrough."
+version: 0.1.0
+author: Hermes Agent
+license: MIT
+metadata:
+  hermes:
+    tags: [corp-v1, discord, channel, delivery, reference]
+    related_skills: [corp-v1-steering-committee, home-v1-discord]
+---
+
+# Corp v1 Delivery Channel Reference
+
+## Overview
+
+This is the central source skill for the `delivery` channel created for each Corp v1 project.
+
+**Current status: setup only.** Its detailed purpose, responsibilities, procedures, artifacts, authority boundaries, and verification rules are intentionally not defined yet. They will be agreed in a separate walkthrough before promotion beyond version `0.1.0`.
+
+## When to Use
+
+Use this source when walking through the future `delivery` channel skill, creating a reviewed project copy after finalization, or comparing an adopted copy with its source.
+
+Do not use this version as complete operating guidance for a live project channel.
+
+## Adoption Contract
+
+After finalization, `corp-v1-steering-committee` requires a project copy named `corp-v1-channel-delivery--<code>` under `corp-v1-<code>-skills-code-agent`. Adoption preserves source history and attribution, applies project context, validates the result, and records the source branch and commit.
+
+Creating existing-project copies is explicitly deferred until separately requested.
+
+## Purpose Definition Pending
+
+The walkthrough must define channel outcomes, responsibilities, activities, artifacts, cross-channel relationships, applicable engineering skills, synchronization behavior, approval boundaries, and verification criteria.
+
+## Common Pitfalls
+
+1. Treating this setup scaffold as finalized policy.
+2. Creating project copies before the requested migration.
+3. Defining behavior indirectly instead of completing the walkthrough.
+4. Losing source history or attribution during adoption.
+
+## Verification Checklist
+
+- [ ] Repository exists under `home-v1-skills-code-agent`.
+- [ ] Default branch is `test`.
+- [ ] Skill name is `corp-v1-channel-delivery`.
+- [ ] Version remains `0.1.0` until purpose is finalized.
+- [ ] No project-scoped copy was created during setup.