beads-workflow
SKILL.md
Canonical bd prefix cutover (2026-04-02)
- Canonical Beads now creates new issues with the
bd-*prefix. - Legacy prefixes remain readable in the shared database via
allowed_prefixesfor historical continuity. - Treat legacy prefixes as carry-forward context only. Do not start new canonical workflow from
af-*or other legacy prefixes when a freshbd-*issue is appropriate. - Under the current local DX model,
bd-*is the default workflow contract for new work in canonical repos.
Beads Workflow Guide
AI-supervised issue tracking with git-backed distributed database.
Command surface: Use bdx for coordination commands. Raw bd is local diagnostics/bootstrap/path-sensitive operations only.
Prefix note: Examples use the Beads prefix for this repo (e.g., bd-xyz). If you are working in another repository, substitute that repo's issue ID prefix everywhere {issue-id} is shown (branch names, Feature-Key trailers, dependency IDs).
In agent-skills, do not rely on the Beads default issue prefix when creating new tracking work. If the active Beads context is af-* or another non-bd-* prefix, create or choose an explicit bd-* issue id before branch, commit, or PR work.
References:
- Beads MCP Plugin: https://github.com/steveyegge/beads/blob/main/docs/PLUGIN.md
- Beads README: https://github.com/steveyegge/beads/blob/main/README.md