coven-task-managerlisted

# Coven Task Manager Use this skill when asked to manage, refresh, audit, triage, or summarize Coven tasks, or when a scheduled automation asks for task-board freshness. ## Sources Start with the Cave task board from the skill directory: ```bash node ./task-manager.mjs report ``` The helper reads `~/.coven/cave-board.json` and writes `~/.coven/task-manager/freshness-report.md` by default. If the canonical repo path is different, run the helper from this skill directory: ```bash node ./task-manager.mjs report --coven-home ~/.coven ``` ## Workflow 1. Load the task board and build a freshness report. 2. Inspect the report sections in this order: `Stale Running`, `Needs Human`, `Ready For Review`, then `Next Actions`. 3. Read `Thread Coordination` before touching individual cards. Treat it as the concurrency control surface for simultaneous sessions. 4. For every active/review/blocked thread, build a small ledger: card id/title, familiar, session id, repo/branch/worktree if known, last evidence checked, current state, and one next action. 5. Resolve collisions before dispatching new work: - If multiple cards share a session, resume that session once and update all linked cards from the same evidence. - If one familiar has multiple active lanes, choose the primary lane and mark the rest as waiting, review, or blocked with a reason. - If multiple lanes touch the same repo or branch, verify branch/worktree ownership before allowing parallel writes. - Prefer resu