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

feat: integrate Kanban channel flow

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-13 16:50:51 +00:00
parent 109428ebcf
commit a212290305
1 changed files with 14 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+14 -9
View File
@@ -1,7 +1,7 @@
---
name: corp-v1-channel-general
description: "Use when operating or synchronizing a Corp v1 project's general channel. Correlates verified activity across the project's general, architecture, delivery, and releases channels; reports overall status, surfaces issues, proposes improvements, and maintains current project-level guidance."
version: 1.2.0
description: "Use when operating or synchronizing a Corp v1 project's general channel. Correlates verified activity across the project's general, architecture, kanban, delivery, and releases channels; reports overall status, surfaces issues, proposes improvements, and maintains current project-level guidance."
version: 1.3.0
author: Hermes Agent
license: MIT
metadata:
@@ -14,7 +14,7 @@ metadata:
## Overview
This skill owns project-level awareness and coordination for a Corp v1 project's `general` channel. It monitors the complete same-project channel set—`general`, `architecture`, `delivery`, and `releases`—and turns verified activity into concise overall updates, issue visibility, maintained guidance, and a durable project-documentation backlog of proposed Epics and Features.
This skill owns project-level awareness and coordination for a Corp v1 project's `general` channel. It monitors the complete same-project channel set—`general`, `architecture`, `kanban`, `delivery`, and `releases`—and turns verified activity into concise overall updates, issue visibility, maintained guidance, and a durable project-documentation backlog of proposed Epics and Features.
It is not a replacement for architecture, delivery, or release ownership. It connects those workstreams, makes their implications visible to the whole project, and routes specialized work to the corresponding channel.
@@ -33,16 +33,17 @@ Do not use it to approve architecture decisions, merge or release code, deploy,
## Approved Information Boundary
Read only the four channels belonging to the same project:
Read only the five channels belonging to the same project:
```text
corp-v1-<code>-general
corp-v1-<code>-architecture
corp-v1-<code>-kanban
corp-v1-<code>-delivery
corp-v1-<code>-releases
```
Read enough mapped-channel history to avoid duplicate updates and only new relevant messages from the other three channels since the previous useful synchronization. Never correlate another project's channels.
Read enough mapped-channel history to avoid duplicate updates and only new relevant messages from the other four channels since the previous useful synchronization. Never correlate another project's channels.
## Core Responsibilities
@@ -179,12 +180,16 @@ A safe update requires:
Changes to governance, authority boundaries, destructive operations, secrets, costs, deployments, or external commitments require explicit approval.
## Kanban Handoff
General preserves authoritative Epic/Feature identity and Scope lifecycle evidence. Kanban consumes these records for active Board and Focus views but must not redefine them. Every status change must retain stable Scope links and approval evidence so Kanban can reconcile flow without inventing state.
## Synchronization Workflow
1. Confirm the exact project code and four approved channel IDs.
2. Read new messages from the other three channels and enough `general` history to avoid duplicates.
1. Confirm the exact project code and five approved channel IDs.
2. Read new messages from the other four channels and enough `general` history to avoid duplicates.
3. Separate facts, approved decisions, proposals, unresolved questions, and failed work.
4. Correlate impact across architecture, delivery, and releases.
4. Correlate impact across architecture, Kanban, delivery, and releases.
5. Inspect Scope navigation, Roadmap, Epics, Features, Ideas, task links, and lifecycle status.
6. Reconcile the Roadmap whenever current or predicted Epic/Feature state changed.
7. Add or materially improve at least one useful evidence-based documentation artifact; never create filler solely to satisfy cadence.
@@ -230,7 +235,7 @@ For completed work include exact evidence such as Discord message IDs, repositor
## Verification Checklist
- [ ] Only the four same-project channels were inspected.
- [ ] Only the five same-project channels were inspected.
- [ ] The update is new, substantive, and deduplicated.
- [ ] Overall status, issues, and cross-channel implications are accurate.
- [ ] Proposals are clearly labeled and routed.