docs: require direct Hermes Kanban links
This commit is contained in:
@@ -11,6 +11,11 @@ metadata:
|
|||||||
|
|
||||||
# Corp v1 UAT Channel
|
# Corp v1 UAT Channel
|
||||||
|
|
||||||
|
|
||||||
|
## 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](<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.
|
||||||
|
|
||||||
## When to Use
|
## When to Use
|
||||||
|
|
||||||
Use this skill when a Corp v1 project needs a distinct UAT stage between Delivery and Releases, a versioned E2E journey repository, or acceptance evidence tied to an exact deployed environment. Do not use it for application implementation, cluster deployment, or release approval.
|
Use this skill when a Corp v1 project needs a distinct UAT stage between Delivery and Releases, a versioned E2E journey repository, or acceptance evidence tied to an exact deployed environment. Do not use it for application implementation, cluster deployment, or release approval.
|
||||||
|
|||||||
Reference in New Issue
Block a user