From hivemind
Manages team goals, KPIs, and action items via the hivemind CLI. Captures tasks with full context for later resumption.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hivemind:hivemind-goalsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
⚠️ **CRITICAL: On this runtime (Hermes), you MUST use the `hivemind` shell CLI for goals + KPIs. DO NOT use `write_file` on `~/.deeplake/memory/goal/...` paths — those writes go to the local filesystem and never reach the team-shared `hivemind_goals` table. Other team members will NOT see them.**
⚠️ CRITICAL: On this runtime (Hermes), you MUST use the hivemind shell CLI for goals + KPIs. DO NOT use write_file on ~/.deeplake/memory/goal/... paths — those writes go to the local filesystem and never reach the team-shared hivemind_goals table. Other team members will NOT see them.
The hivemind-memory skill describes a generic memory layout — it does NOT apply to goals/KPIs. For goals/KPIs, use the CLI below.
hivemind goal add "<text>" # create goal, prints goal_id
hivemind goal list [--mine|--all] # list (default --mine)
hivemind goal done <goal_id> # mark closed
hivemind goal progress <goal_id> <opened|in_progress|closed>
hivemind kpi add <goal_id> <kpi_id> <target> <unit> [name] # add KPI to goal
hivemind kpi list <goal_id> # list KPIs for goal
hivemind kpi bump <goal_id> <kpi_id> <delta> # increment current (int)
hivemind goal add "<short description>" — capture stdout, that's the goal_id (UUID).hivemind kpi add <goal_id> <slug> <target> <unit> per KPI.When the user parks a tangential task mid-session — "save this for later", "remind me to …", "don't let me forget …", "let's do X later" — store enough context to resume cold later, not just a one-liner. Tag it --agent capture so parked side-tasks are separable from hand-made goals:
hivemind goal add --agent capture "Add rate-limiting to the webhook handler
Start here: add a per-IP token bucket on the handler entry path
Files: src/webhook/handler.ts:120-160, src/webhook/limits.ts
Branch: feat/webhook-hardening
Run: pnpm test webhook
Why: bursty clients hammer the endpoint; defer until retry-backoff lands"
Line 1 is the label (what goal list shows). Fill Start here / Files / Branch / Run / Why from the conversation; Start here: matters most. Pass the whole package as one double-quoted argument so the newlines are preserved.
When the user says "let's work on that task / goal" or "pick up the <X> task":
hivemind goal list --mine — match the user's reference to a goal_id.hivemind goal get <goal_id> — prints the full package (goal list shows only the first line, so always use goal get). Read it as your working context.hivemind goal progress <goal_id> in_progress — mark it started.Start here: using the Files / Branch / Run lines. Continue as if the context was never lost.write_file on any path under ~/.deeplake/memory/goal/ or ~/.deeplake/memory/kpi/.mkdir / cat > to create those files manually via terminal.If the user wants to inspect goals you created, run hivemind goal list --mine (terminal) and present the output.
npx claudepluginhub legioncodeinc/hivemindGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.