corp-v1-3darch-skills-code-agent/corp-v1-channel-kanban-3darch
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: monitor Scope lifecycle state

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-13 19:33:32 +00:00
parent 0f2ac72e7a
commit b4ed7af2a7
1 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+10 -9
View File
@@ -1,7 +1,7 @@
---
name: corp-v1-channel-kanban
description: "Use when operating or synchronizing a Corp v1 project's Kanban channel. Maintains the project Kanban Board and Focus views across Epic, Feature, and task state; correlates all five same-project channels; and records human approval before tasks enter Delivery's executable InBacklog queue."
version: 1.1.0
description: "Use when operating or synchronizing a Corp v1 project's Kanban channel. Maintains Board and Focus across Epic, Feature, and task state; correlates all six same-project channels; and records human approval before tasks enter Delivery's executable InBacklog queue."
version: 1.2.0
author: Hermes Agent
license: MIT
metadata:
@@ -14,9 +14,9 @@ metadata:
## Overview
This skill owns flow visibility and task-readiness coordination for a Corp v1 project's `kanban` channel. It monitors the five same-project channels—`general`, `architecture`, `kanban`, `delivery`, and `releases`—and maintains the project documentation's top-level **Kanban** area.
This skill owns flow visibility and task-readiness coordination for a Corp v1 project's `kanban` channel. It monitors the six same-project channels—`general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`—and maintains the project documentation's top-level **Kanban** area.
Kanban does not replace product scope, architecture, implementation, or release ownership. General owns Epics and Features; Architecture owns requirements, design, task decomposition, dependencies, implementation approval, and version allocation; Kanban exposes flow and obtains human approval for ready tasks to enter Focus `InBacklog`; Delivery executes those approved tasks; Releases owns release readiness and controlled release preparation.
Kanban does not replace product scope, architecture, implementation, or release ownership. Scope owns Roadmap, Ideas, Epics, and Features; Architecture owns requirements, design, task decomposition, dependencies, implementation approval, and version allocation; Kanban exposes flow and obtains human approval for ready tasks to enter Focus `InBacklog`; Delivery executes those approved tasks; Releases owns release readiness and controlled release preparation.
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.
@@ -40,13 +40,14 @@ Inspect only:
```text
corp-v1-<code>-general
corp-v1-<code>-scope
corp-v1-<code>-architecture
corp-v1-<code>-kanban
corp-v1-<code>-delivery
corp-v1-<code>-releases
```
Read enough mapped-channel history to avoid duplicates and only relevant new activity from the other four channels. Never inspect or correlate another project's channels.
Read enough mapped-channel history to avoid duplicates and only relevant new activity from the other five channels. Never inspect or correlate another project's channels.
## Human Approval Gate
@@ -133,8 +134,8 @@ If no task is ready, document the exact dependency or approval gate preventing F
## Synchronization Workflow
1. Confirm the exact project code and five approved channel IDs.
2. Read new messages from the other four channels and enough Kanban history to avoid duplicates.
1. Confirm the exact project code and six approved channel IDs.
2. Read new messages from the other five channels and enough Kanban history to avoid duplicates.
3. Fetch authoritative Scope, Architecture, Delivery, and Releases records.
4. Separate verified facts, human decisions, proposals, derived state, blockers, and contradictions.
5. Reconcile Board and Focus while preserving ownership and links.
@@ -148,7 +149,7 @@ If no task is ready, document the exact dependency or approval gate preventing F
May autonomously:
- read and correlate the five same-project channels;
- read and correlate the six same-project channels;
- maintain Board and Focus from verified authoritative state;
- calculate derived aggregate states when labeled;
- remove terminal work from active views while preserving history;
@@ -184,7 +185,7 @@ Include exact project documentation paths, item IDs, source links, human decisio
## Verification Checklist
- [ ] Only the five same-project channels were inspected.
- [ ] Only the six same-project channels were inspected.
- [ ] Kanban appears immediately after Architecture and has its own Board/Focus sidebar.
- [ ] Board uses only `InIdeation`, `InBacklog`, `InProgress`, and `ToBeReleased`.
- [ ] Board contains only unfinished Epics and Features.