feat: include Scope in project context

This commit is contained in:
2026-08-13 19:33:33 +00:00
parent a4612a2087
commit ee61218052
+4 -3
View File
@@ -1,7 +1,7 @@
--- ---
name: corp-v1-channel-delivery 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." 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.3.0 version: 1.4.0
author: Hermes Agent author: Hermes Agent
license: MIT license: MIT
metadata: metadata:
@@ -14,7 +14,7 @@ metadata:
## Overview ## Overview
This skill owns delivery health for a Corp v1 project. It monitors the project's `general`, `architecture`, `kanban`, `delivery`, and `releases` channels and implements only tasks whose parent Feature has explicit human `Approved for Implementation` evidence and which a human team member separately admitted to Kanban Focus `InBacklog`. This skill owns delivery health for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases` channels and implements only tasks whose parent Feature has explicit human `Approved for Implementation` evidence and which a human team member separately admitted to Kanban Focus `InBacklog`.
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. 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.
@@ -54,10 +54,11 @@ Every delivery iteration must complete at least one useful, safe activity for an
## Approved Information Boundary ## Approved Information Boundary
Inspect only the project's five channels: Inspect only the project's six channels:
```text ```text
corp-v1-<code>-general corp-v1-<code>-general
corp-v1-<code>-scope
corp-v1-<code>-architecture corp-v1-<code>-architecture
corp-v1-<code>-kanban corp-v1-<code>-kanban
corp-v1-<code>-delivery corp-v1-<code>-delivery