69e8fb1f6d
Thanks for accepting the original contribution! I've made some updates based on real-world usage. Some of the examples in the original were a bit idiosyncratic to my own work, so I've generalized them to use universal programming scenarios (authentication, database migrations, API design) that should be more relatable to any developer. I've also added some broader improvements to the skill. Apologies for not doing these as two separate pull requests - I hope bundling them together is OK. These improvements came largely from asking Claude to reflect on what was useful and difficult about using the skill - in particular, Claude felt that the post-compaction scenario was a powerful one because normally a context compaction causes severe loss of state. Main changes: - Add comprehensive compaction survival guide with note-taking patterns - Replace basic TodoWrite integration with temporal layering pattern - Add bd export/import documentation with collision resolution - Clarify when to ask before creating issues vs creating directly - Add database discovery rules for multi-DB scenarios
Beads Examples
This directory contains examples of how to integrate bd with AI agents and workflows.
Examples
- python-agent/ - Simple Python agent that discovers ready work and completes tasks
- bash-agent/ - Bash script showing the full agent workflow
- markdown-to-jsonl/ - Convert markdown planning docs to bd issues
- github-import/ - Import issues from GitHub repositories
- git-hooks/ - Pre-configured git hooks for automatic export/import
- branch-merge/ - Branch merge workflow with collision resolution
- claude-desktop-mcp/ - MCP server for Claude Desktop integration
- claude-code-skill/ - Claude Code skill for effective beads usage patterns
Quick Start
# Try the Python agent example
cd python-agent
python agent.py
# Try the bash agent example
cd bash-agent
./agent.sh
# Install git hooks
cd git-hooks
./install.sh
# Try branch merge collision resolution
cd branch-merge
./demo.sh
Creating Your Own Agent
The basic agent workflow:
- Find ready work:
bd ready --json --limit 1 - Claim the task:
bd update <id> --status in_progress --json - Do the work: Execute the task
- Discover new issues:
bd create "Found bug" --json - Link discoveries:
bd dep add <new-id> <parent-id> --type discovered-from - Complete the task:
bd close <id> --reason "Done" --json
All commands support --json for easy parsing.