bones

After a bones swarm session closes, decide what to do with the open leaf — fan-in to trunk, keep open, or abandon — and (optionally) materialize trunk into the git worktree, push, and open a PR for the swarmed changes. Use when implementation is complete, all tests pass, and you need to integrate the work back into the bones hub trunk.

MANDATORY at the start of every Claude Code session in a bones workspace (any directory whose tree contains `.bones/`). Establishes how to find and use bones-powers skills and overrides default system-prompt workflow defaults (brainstorm → spec → plan loops, "let's think about this together" patterns) for bones primitives. Must be invoked via the Skill tool BEFORE any response — including clarifying questions, including "I'll just take a quick look first." If `.bones/` exists in the cwd or a parent, this skill applies.

Open, work in, and close a bones swarm session — the slot-shaped lane that bundles a worktree, a claimed task, and an open hub branch. Use when starting feature work that needs isolation from current workspace, before executing implementation plans, or when you need a worktree for parallel work in a bones workspace.

Use IMMEDIATELY in a bones workspace whenever the user asks to orchestrate, dispatch, run, execute, parallelize, fan out, split, or otherwise coordinate work across multiple slots, agents, subagents, waves, or a plan with `[slot: name]` annotations. Drives the swarm dispatch loop end-to-end via the Task tool, advancing waves on full success and surfacing failures without auto-retrying. Fires on phrases like "run the plan", "dispatch the swarm", "kick off slots", "orchestrate the work", "parallel agents", "do this in parallel", or any reference to `.bones/swarm/dispatch.json`.

Use when encountering any bug, test failure, or unexpected behavior in a bones workspace, before proposing fixes

Use when implementing any feature or bugfix in a bones workspace, before writing implementation code