From 91ea1744a943f2bc22ee52fd18b74dbac1e6fa11 Mon Sep 17 00:00:00 2001 From: Jarvis Jr Hermes Date: Thu, 13 Aug 2026 16:50:52 +0000 Subject: [PATCH] feat: gate delivery through Kanban Focus --- SKILL.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/SKILL.md b/SKILL.md index d49343c..a2a2cb0 100644 --- a/SKILL.md +++ b/SKILL.md @@ -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.1.0 +version: 1.2.0 author: Hermes Agent license: MIT metadata: @@ -14,7 +14,7 @@ metadata: ## Overview -This skill owns delivery health for a Corp v1 project. It monitors the project's `general`, `architecture`, `delivery`, and `releases` channels and implements only Features that architecture documentation marks `Approved for Implementation` through an explicit human team-member decision. +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`. 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. @@ -42,20 +42,22 @@ Before starting or continuing Feature implementation, verify in project document - task breakdown and dependencies; - target version and status; - acceptance evidence expected from delivery. +- explicit human Kanban approval admitting the exact task to Focus `InBacklog`. -Hermes cannot approve a Feature for implementation. If the gate is incomplete, improve safe delivery-readiness documentation or raise the exact missing decision in `architecture`; do not start code. +Hermes cannot approve a Feature for implementation or admit a task to Focus `InBacklog`. If the gate is incomplete, improve safe delivery-readiness documentation or raise the exact missing decision in `architecture`; do not start code. ## Proactive Iteration Requirement -Every delivery iteration must complete at least one useful, safe activity for an implementation-approved Feature or delivery-health need: implement an unblocked task, add tests, diagnose/fix CI, improve build tooling, update real Ways of Working/Engineering guidance, verify dependency readiness, or document a concrete blocker with evidence. Never create filler changes. Select work from architecture's approved task/dependency plan and update progress in project documentation. +Every delivery iteration must complete at least one useful, safe activity for an implementation-approved Feature or delivery-health need: implement an unblocked task, add tests, diagnose/fix CI, improve build tooling, update real Ways of Working/Engineering guidance, verify dependency readiness, or document a concrete blocker with evidence. Never create filler changes. Select work only from Kanban Focus `InBacklog`, backed by architecture's approved task/dependency plan, and update progress in project documentation. ## Approved Information Boundary -Inspect only the project's four channels: +Inspect only the project's five channels: ```text corp-v1--general corp-v1--architecture +corp-v1--kanban corp-v1--delivery corp-v1--releases ``` @@ -144,7 +146,7 @@ Update these pages from verified project practice. Do not document a planned pro ## Synchronization Workflow 1. Read new same-project activity and enough delivery history to avoid duplicates. -2. Verify human `Approved for Implementation` evidence, task dependencies, and target version before Feature work. +2. Verify human `Approved for Implementation` evidence, explicit human Kanban Focus `InBacklog` admission, task dependencies, and target version before task work. 3. Identify executable tasks, CI failures, blockers, requirements/ADR implications, and documentation drift. 4. Load all applicable project engineering skills. 5. Complete at least one useful safe activity when an authorized path exists; otherwise document and route the exact blocker. @@ -186,7 +188,7 @@ Include repository, branch, commit SHA, changed paths, commands, local results, 7. Repeatedly posting unchanged failure summaries. 8. Inspecting another project. 9. Starting implementation because requirements exist but human implementation approval is absent. -10. Ignoring architecture task dependencies or target-version allocation. +10. Ignoring architecture task dependencies, Kanban Focus admission, or target-version allocation. 11. Posting passive status when safe implementation, testing, diagnosis, or documentation work is available. ## Verification Checklist @@ -194,7 +196,7 @@ Include repository, branch, commit SHA, changed paths, commands, local results, - [ ] Only same-project channels and repositories were used. - [ ] Work maps to approved requirements/architecture. - [ ] Feature has explicit human `Approved for Implementation` evidence and a documented target version. -- [ ] Selected tasks respect documented dependencies. +- [ ] Selected tasks respect documented dependencies and have explicit human Focus `InBacklog` admission. - [ ] At least one useful delivery activity was completed, or a concrete blocker was documented and routed. - [ ] Applicable project skills were loaded. - [ ] Tests and builds were actually run.