What problem does it solve? Coordinating issue tracking across a multi-repo umbrella workspace is error-prone: tasks live in per-repo beads databases while reads must span an aggregate view, and writing to the wrong repo breaks ownership and sync. This Skill provides the operating manual for reading, creating, updating, closing, and linking beads issues correctly through the in-process beads_* tools. ## Core Features & Use Cases - Cross-repo reads: Query ready, open, stale, or blocked issues across every repo from the aggregate view using beads_ready, beads_list, beads_show, and beads_deps. - Routed writes: Create, update, close, reopen, and comment on issues with automatic routing to the owning repo based on the id prefix, including ephemeral wisp creation and promotion. - Dependency and epic management: Link blockers within a repo, build epic hierarchies with parent/child tasks, and instantiate molecule workflows with gates. - Use Case: While triaging a sprint, call beads_ready with a label filter to find unblocked work, claim an issue, create subtasks under an epic in the correct repo, then close everything with a reason when done. ## Quick Start Ask the assistant to show ready beads tasks across all repos and claim the highest-priority one to start work.
