Board Knowledge

Share and search findings on a Kanban board KB.

Skill metadata

Source	Bundled (installed by default)
Path	skills/memory/board-knowledge
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	memory, kanban, board-kb, multiagent, research
Related skills	archival-recall, episodic-diary, progress-ledger

Reference: full SKILL.md

信息

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Board Knowledge Skill

Use the Board Memory OS tier for project findings shared by every profile on the same Kanban board. This is the only intentional cross-profile memory share. Do not put Board facts into Core/MEMORY.md unless they are stable personal preferences.

Storage: kanban/boards/<slug>/kb/findings.jsonl (via vibeos kanban kb).

When to Use

• Orchestrator starts a swarm / multi-task plan on a board — search KB first.
• Researcher or worker discovers a durable project fact (URL, price, decision).
• Another profile on the same board needs what you already found.
• Closing a Kanban task with findings that should outlive the task comment.

Do not use Board KB for:

• Personal prefs that follow you across projects → User / Archival.
• Chat diary (“what we discussed yesterday”) → Episodic.
• Secrets, tokens, passwords → never write them to KB.

Prerequisites

• Active Kanban board (vibeos kanban boards show / --board <slug>).
• Workers pinned with VIBEOS_KANBAN_BOARD (dispatcher does this).
• Shell access to run vibeos kanban kb … via terminal.

How to Run

# Before planning — what does the team already know?
vibeos kanban kb search "pricing" --limit 10
vibeos kanban kb list --limit 20

# After a durable finding (tie to task + path:line when possible)
vibeos kanban kb add --task T12 --confidence 0.85 \
  --kind finding --tags pricing \
  --cite docs/pricing.md:12 --sha "$(git rev-parse --short HEAD)" \
  "Competitor X lists Pro at $12/mo (public pricing page, 2026-07)."

# Substring (default) or token-overlap ranking (no embeddings)
vibeos kanban kb search "pricing"
vibeos kanban kb search "competitor pricing page" --semantic

# Pin board when not on the default
vibeos kanban --board alpha kb search sources
vibeos kanban kb path

Finding format

Keep bodies short (1–3 sentences). Include:

1. Claim — the fact itself.
2. Provenance — URL, doc name, or “from task T…”.
3. Confidence — 0.0–1.0 (--confidence); lower if inferred.

Field	CLI	Notes
body	--body / positional	Required
task_id	--task	Prefer always for swarm work
confidence	--confidence	Default 0.7
kind	--kind	finding / decision / source
tags	--tags	Comma-separated
author	--author	Defaults to profile
citations	--cite path[:line]	Repeatable; optional --sha
search	--semantic	Token-overlap rank; no embeddings

Procedure (Orchestrator)

1. vibeos kanban kb search <topic> before spawning or assigning work.
2. Put relevant hits into the task body / Progress Ledger — not into Core.
3. Tell workers: “write durable project facts with kanban kb add --task …”.
4. On stall / promote: search again so you do not rediscover the same fact.

Procedure (Worker / Researcher)

1. When a fact will matter after this task ends → kb add with --task.
2. Prefer one finding per entry (searchable); avoid dumping whole reports.
3. If unsure the fact is board-scoped vs personal → Archival (your profile) instead.

Quick Reference

Action	Command
Add	vibeos kanban kb add --task ID --confidence 0.8 "…"
List	vibeos kanban kb list [--task ID]
Search	vibeos kanban kb search "query"
Path	vibeos kanban kb path

Pitfalls

• Wrong board — always check boards show / --board; KB never merges boards.
• Core pollution — Board facts do not belong in MEMORY.md by default.
• Auto-promote myth — from-delegation and KB writes are manual (or skill-guided); nothing invents Kanban tasks from chat alone.
• Leaf memory tool — subagents still cannot call Core memory; Board KB CLI is the share path.

Verification

• vibeos kanban kb add then kb search returns the entry on the same board.
• A second profile on that board can kb list and see the entry.
• The same query on another board returns nothing (isolation).