hermes - 💡(How to fix) Fix Standardize Kanban/delegation handoff and verification evidence schema

Motivation

Cursor's orchestrate plugin has mature patterns for multi-agent task trees that map well to Hermes Kanban/delegation, without needing Cursor runtime installation:

• Structured worker/subplanner/verifier handoffs.
• Synthetic failure handoffs when an agent dies silently.
• Verification quality labels (live-ui-verified, unit-test-verified, type-check-only, verifier-blocked, verifier-failed).
• Dependency handoff relay so downstream workers receive upstream context explicitly.
• Retry policy based on classified failure modes.

Hermes already has Kanban, cron, delegation, and background processes. The compatible adaptation is to tighten Hermes-native task handoffs and verifier evidence so long-running coding ops converge with less ambiguity.

Proposed Hermes adaptation

Enhance Kanban/delegation coding workflows with a standard handoff schema:

## Status
success | partial | blocked | error

## Branch
<branch or none>

## What I did
- ...

## Verification
live-ui-verified | unit-test-verified | type-check-only | verifier-blocked | verifier-failed

## Execution
- <command> -> <outcome>

## Notes / concerns
- ...

## Suggested follow-ups
- ...

Add support for synthetic failure handoffs from durable worker runners where possible, with classified causes such as cap-hit, OOM, network-drop, tool-error, unknown.

Acceptance criteria

• Document the handoff schema in a built-in Hermes coding/kanban skill or docs page.
• Kanban worker prompts ask for the schema for coding tasks.
• Dashboard/digest jobs can classify a task/PR as verified, weakly verified, blocked, or failed based on the handoff.
• Failure handoffs are generated or at least recommended when a worker exits without a useful final message.

Source pattern reviewed

• cursor/plugins/orchestrate at d1cdb88
• Especially references/handoffs.md, prompts/worker.md, and verifier semantics.