Kategoriserer danske regnskabs-/ERP-skills, ERP-data-afstemnings-
skill og to devops-workflows (gitea-issue-agent, kanban-workflows)
som Radix-medlemmers AI-agenter kan dele.
Struktur:
skills/<kategori>/<skill-navn>/SKILL.md
skills/<kategori>/<skill-navn>/{references,templates,scripts}/
Indekseret af index.json (genereret af scripts/rebuild_index.py).
Kør `python3 scripts/rebuild_index.py --check` i CI for at fange
synkroniseringsfejl.
2.0 KiB
name, description, version, author, license, metadata
| name | description | version | author | license | metadata | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| kanban-workflows | Use when operating Hermes Kanban workflows: decomposing work as an orchestrator, executing as a worker, managing lanes, status, blockers, and reconciliation. | 1.0.0 | Hermes Agent | MIT |
|
Kanban Workflows Umbrella
Overview
Kanban work has two sides: orchestrators decompose and route work without doing it themselves; workers execute a scoped card, keep status current, and return verifiable evidence. Use this umbrella for both roles.
When to Use
- Acting as a Hermes Kanban orchestrator.
- Acting as a Hermes Kanban worker.
- Deciding whether to split, assign, block, or reconcile cards.
- Handling worker pitfalls, examples, and edge cases.
Role Playbooks
Orchestrator
Decompose outcomes into cards small enough for one worker, include acceptance criteria, and avoid the temptation to implement the work directly. Route work, unblock workers, and reconcile results.
Worker
Own exactly the assigned card. Update status when starting, blocked, or done. Run the requested checks and return concise evidence: files changed, commands run, output, and remaining risks.
Lanes and external agents
If a worker uses an external coding agent lane, keep Kanban as the source of truth and verify the lane's output before closing the card.
Common Pitfalls
- Orchestrators doing implementation work themselves.
- Workers broadening scope beyond the card.
- Closing cards from self-reports without independent verification.
- Losing blocker state instead of surfacing it promptly.
Package Notes
Archived source skills retain the deeper role-specific text: kanban-orchestrator and kanban-worker.
Verification Checklist
- Card scope and acceptance criteria are explicit.
- Exactly one owner is responsible for each action.
- Status reflects reality: pending, in progress, blocked, done.
- Completion includes verifiable evidence.