Loading...
Loading...
Found 8 Skills
Guide for operating the bitdrift bd CLI and analyzing live bitdrift account data — workflows, charts, sessions, issues, keys, connectors, and app health investigations. Trigger when the user wants to run bd commands, inspect live platform data, debug an app with bitdrift, create or edit workflows, read charts or metrics, triage crashes, inspect session timelines, or automate bitdrift operations from the CLI.
Help users study research papers with Paper Breakdown. Use when the user wants to study, understand, ask questions about, summarize, or analyze a paper with Paper Breakdown, including requests like "I want to study paper P with Paper Breakdown", "help me read this paper in PaperBD", "use Paper Breakdown for this arXiv paper", or similar requests about looking up a paper, finding its arXiv ID, checking access in the paperbd CLI, and then answering questions about the paper.
This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what's ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.
Epic decomposition into trackable issues. Triggers: "create a plan", "plan implementation", "break down into tasks", "decompose into features", "create beads issues from research", "what issues should we create", "plan out the work".
Track tasks and issues using the bd CLI. Use for task management, sprint planning, dependency tracking, and project organization. Replaces TodoWrite.
File Beads epics/issues from a finalized plan/spec AND do the polish pass (clarity, acceptance criteria, sizing, deps). Use when asked to create Beads from a plan/spec (OpenSpec, PRD, design doc), convert an external plan into Beads structure, or review/refine an existing Beads set.
GainForest beads (`bd`) planning workflow. Activates on ALL user work requests — task planning, epic management, claiming work, closing tasks with commit links, handling blockers. Use before writing any code.
Use when working with the beads (bd) CLI for issue tracking, managing epics and tasks, handling dependencies, or starting/ending coding sessions with persistent work tracking