docs: promote reusable AeroSim channel lessons

This commit is contained in:
jarvis-at-skic committed 2026-10-20 18:42:43 +00:00
1 parent e8507ad718
commit 26cbf12bc6
5 files changed
+113 -24

No files matched your search

+21 -11
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 Board and Focus across Epic, Feature, and task state; correlates all seven same-project channels; and records exact admission before tasks enter the READY_FOR_DELIVERY pickup queue."
version: 1.7.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 eight same-project channels; and records exact admission before tasks enter the READY_FOR_DELIVERY pickup queue."
version: 1.8.0
author: Hermes Agent
license: MIT
metadata:
@@ -18,7 +18,7 @@ metadata:
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.
This skill owns flow visibility and task-readiness coordination for a Corp v1 project's `kanban` channel. It monitors the seven same-project channels—`general`, `scope`, `architecture`, `ui-ux`, `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 eight same-project channels—`general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, `uat`, and `releases`—and maintains the project documentation's top-level **Kanban** area.
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 records the exact admission that moves an eligible task to Focus `READY_FOR_DELIVERY`; Delivery claims that task and records `IN_PROGRESS`; Releases owns release readiness and controlled release preparation.
@@ -75,6 +75,8 @@ This execution boundary was approved by RootAtSkic (`discord:1518725627845283888
## Approved Information Boundary
Follow the eight-channel topology in `corp-v1-main`, approved by Board message `1552966246591365123`; include UAT between Delivery and Releases. Verify mapped IDs and effective access before reading.
Inspect only:
```text
@@ -84,10 +86,11 @@ corp-v1-<code>-architecture
corp-v1-<code>-ui-ux
corp-v1-<code>-kanban
corp-v1-<code>-delivery
corp-v1-<code>-uat
corp-v1-<code>-releases
```
Read enough mapped-channel history to avoid duplicates and only relevant new activity from the other six 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 seven channels. Never inspect or correlate another project's channels.
## Human Approval Gate
@@ -116,7 +119,7 @@ Focus
### Board
Board provides a visual board of all unfinished Epics and Features grouped into these flow columns. `ReadyForDelivery` is the presentation mapping of canonical delivery status `READY_FOR_DELIVERY`; do not create aliases such as `READY` or `QUEUED`:
Board provides a visual board of all unfinished Epics and Features grouped into these flow columns. `ReadyForDelivery` represents the exact-task `READY_FOR_DELIVERY` admission gate, separate from Scope-owned canonical delivery status; do not create aliases such as `READY` or `QUEUED`:
1. `InIdeation`
2. `InBacklog`
@@ -134,7 +137,7 @@ Board statuses mean:
- `InProgress` — active solution or implementation work exists.
- `ToBeReleased` — implementation is complete enough for release readiness; release approval and execution remain separate.
If source lifecycle states are more detailed, maintain an explicit deterministic mapping to these four board states. Never change authoritative approval history merely to simplify Board display.
If source lifecycle states are more detailed, maintain an explicit deterministic mapping to these five board columns. Never change authoritative approval history merely to simplify Board display.
### Focus
@@ -186,10 +189,15 @@ Use authoritative ownership:
- requirements, architecture, task definitions/dependencies, implementation approval, version allocation → Architecture;
- exact `READY_FOR_DELIVERY` Focus admission decision → Kanban human decision;
- task execution progress and completion evidence → Delivery;
- frozen-deployment acceptance verdict and defect-return evidence → UAT;
- release readiness, released state, and post-release outcome → Releases.
When sources conflict, do not choose silently. Mark the card as blocked or inconsistent, link both sources, and route the contradiction to the owning channel.
A healthy deployment without approved scope and exact-task admission is an **execution-to-governance contradiction**, not retroactive readiness. Preserve application source, deployed revision, artifact identity, runtime observations and any template/rendered-source divergence separately. Do not add the unmapped work to Focus or a release candidate; preserve unrelated valid Focus items. Route each missing decision to its owner. See [recurring refresh](references/recurring-refresh-and-publication.md#live-deployment-evidence-without-a-governed-item-mapping).
Board columns are presentation, not a replacement lifecycle. Keep canonical delivery status, admission, approval, blocking and acceptance verdicts separate. UAT owns the evidence-grounded acceptance verdict for the frozen tested deployment; it does not create another Task status or authorize release. Read only the mapped same-project UAT channel; topology is not mutation authority.
## Proactive Iteration Requirement
Every iteration must materially improve one useful, evidence-based Kanban artifact when possible: reconcile state, remove terminal cards from Board, repair links, expose a blocker, update hierarchy, prepare a task-readiness package, record a human Focus decision, or improve stale ownership/dependency/version evidence. Never create filler or autonomously advance approval-gated state.
@@ -202,9 +210,9 @@ For frontend-affecting tasks, Kanban includes the approved UI/UX design-package
## Synchronization Workflow
1. Confirm the exact project code and seven approved channel IDs.
2. Read new messages from the other six channels and enough Kanban history to avoid duplicates.
3. Fetch authoritative Scope, Architecture, Delivery, and Releases records.
1. Confirm the exact project code and eight approved channel IDs.
2. Read new messages from the other seven channels and enough Kanban history to avoid duplicates.
3. Fetch authoritative Scope, Architecture, Delivery, UAT, 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.
6. Remove terminal Epic/Feature cards from Board and terminal items from Focus without deleting history.
@@ -217,7 +225,7 @@ For frontend-affecting tasks, Kanban includes the approved UI/UX design-package
May autonomously:
- read and correlate the seven same-project channels;
- read and correlate the eight 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;
@@ -257,6 +265,8 @@ Use two-pass channel evidence collection, distinguish substantive messages from
When bootstrapping or structurally repairing Kanban documentation, preserve dedicated Board/Focus information architecture, semantic empty states, fail-closed validators, exact-head CI, and authenticated artifact readback. Follow [references/kanban-bootstrap-and-validation.md](references/kanban-bootstrap-and-validation.md).
Source comparison and exclusions: [AeroSim lessons review](references/aerosim-lessons-review.md).
## Common Pitfalls
1. Treating Kanban as a second source of truth for Scope or Architecture.
@@ -273,7 +283,7 @@ When bootstrapping or structurally repairing Kanban documentation, preserve dedi
## Verification Checklist
- [ ] Only the seven same-project channels were inspected.
- [ ] Only the eight same-project channels were inspected.
- [ ] The session changed no project implementation repository; project-repository writes were limited to the dedicated Kanban documentation area and its minimum required wiring.
- [ ] Any implementation request was represented in planning/Board/Focus and handed to Delivery rather than executed or delegated from Kanban.
- [ ] Kanban appears immediately after Architecture and has its own Board/Focus sidebar.