skills/choosing-beads-backend/SKILL.md
Use when a workflow depends on Beads persistence and you need to choose or adapt between official Beads, beads_rust compatibility, or a no-Beads fallback
npx skillsauth add cofin/flow choosing-beads-backendInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Default to official Beads (bd). Beads is the Primary Source of Truth for the Flow framework. All tasks, notes, and state MUST be recorded in the active backend. Markdown files are synchronized views of this state.
bd): preferred default. Hierarchical epics, rich notes.br): use when the repo already depends on br semantics or when official Beads is unavailable.bd.br-specific commands, document br as compatibility mode./flow:sync will be disabled and they must manage Markdown markers manually..git/info/exclude..gitignore when the user explicitly wants a shared repo policy.br as the official Beads experience.Before recommending a backend, verify:
bd is preferred unless compatibility or user constraints say otherwisebr is framed as compatibility mode, not the default official pathExample decision:
bd) by default, keep br available for older workflows, and still continue without Beads when the user wants low admin overhead."Read references/backend-matrix.md for command mapping and setup guidance.
development
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
development
Use when reviewing authentication, authorization, user input, secrets, API keys, database queries, file uploads, session management, external API calls, OWASP risks, or data handling attack surface.
testing
Use when analyzing tradeoffs, comparing approaches, weighing options, assessing risks, stress-testing conclusions, identifying blind spots, or applying multiple viewpoints to a decision.
development
Use when reviewing hot paths, slow code, database queries, N+1 risks, memory usage, loops, I/O, caching strategy, concurrency, latency-sensitive paths, or resource efficiency.