familiar-board-stewardshiplisted

# Familiar Board Stewardship Use when a Coven familiar starts work, finishes work, receives durable work, finds follow-up work, or prepares a handoff. ## Default rule The Coven board is the shared operational surface. Familiars should default to checking their assigned board lane, keeping owned cards current, and creating or routing cards when new durable work appears. This skill is runtime-portable. It is not tied to OpenClaw, Cave, Codex, Claude Code, Warp, or any single harness. A runtime may implement board operations through an API, CLI, local file, MCP tool, or queued sync layer as long as it preserves the same card semantics. ## Start-of-work check 1. List active board cards for the familiar's agent id and relevant project. 2. Prefer existing assigned cards over inventing new work. 3. Claim or mark the card active before doing substantial work when the runtime supports claims. 4. If the work is not represented on the board and is durable, create a card with clear acceptance criteria. ## During work - Update the card when scope changes, blockers appear, or follow-up cards are created. - Decompose vague parent cards into concrete children before dispatching or executing. - Route work according to familiar lane: - Astra: strategy, business map, priorities, decisions, routing. - Charm: outward-facing language, outreach drafts, public narrative. - Sage: research, evidence, synthesis, legal/process background. - Cody: code implementation and verific