From 602b1a0afdac56f4b8a10def4bd241b53495c3e3 Mon Sep 17 00:00:00 2001 From: Jarvis Jr Hermes Date: Wed, 23 Sep 2026 19:05:03 +0000 Subject: [PATCH] docs: require direct Hermes Kanban links --- SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/SKILL.md b/SKILL.md index 4f3b7c1..86d2ef7 100644 --- a/SKILL.md +++ b/SKILL.md @@ -14,6 +14,10 @@ metadata: ## Overview +## Hermes Kanban direct-link contract + +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](/kanban?board=)`. 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 product discovery and durable scope for a Corp v1 project's `scope` 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 **Scope** area. Scope owns Overview, Roadmap, Epics, Features, canonical Task records/reader pages, Ideas, and Questions. General coordinates overall project awareness but does not duplicate Scope records. Architecture performs solution work only for Features explicitly approved for solution by a human team member and remains semantic owner of requirement/task derivation, dependencies, and readiness. Hermes participates proactively by proposing and refining useful scope, but never approves its own proposals.