docs: promote reusable AeroSim channel lessons
This commit is contained in:
1 parent
0bf71b905f
commit
5a0949658d
4 files changed
+106
-8
No files matched your search
@@ -1,7 +1,7 @@
|
||||
---
|
||||
name: corp-v1-channel-delivery
|
||||
description: "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."
|
||||
version: 1.13.0
|
||||
version: 1.14.0
|
||||
author: Hermes Agent
|
||||
license: MIT
|
||||
metadata:
|
||||
@@ -42,7 +42,7 @@ Never invent, abbreviate, or substitute lifecycle values such as `Ready`, `Activ
|
||||
|
||||
A merge or successful CI does not automatically mean `DONE`. Releasable application Tasks normally move from `IN_PROGRESS` to `TO_BE_RELEASED`; `DONE` requires the applicable release or completion evidence. Status reports must show the exact canonical value even when a separate plain-language action is also included.
|
||||
|
||||
This skill owns delivery health for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, 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.
|
||||
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.
|
||||
|
||||
@@ -120,7 +120,7 @@ Every delivery iteration must complete at least one useful, safe activity for an
|
||||
|
||||
## Approved Information Boundary
|
||||
|
||||
Inspect only the project's seven channels:
|
||||
Inspect only the project's eight channels:
|
||||
|
||||
```text
|
||||
corp-v1-<code>-general
|
||||
@@ -129,6 +129,7 @@ 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
|
||||
```
|
||||
|
||||
@@ -260,6 +261,8 @@ Include repository, branch, commit SHA, changed paths, commands, local results,
|
||||
|
||||
## Mined Project-Adoption Improvements
|
||||
|
||||
Review provenance and exclusions: [AeroSim lessons review](references/aerosim-lessons-review.md).
|
||||
|
||||
## 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.
|
||||
|
||||
Reference in new issue
Block a user