title: Add export/import commands

description: Support bd export --format=jsonl and bd import for text-based git workflow

status: open

issue_type: feature


title: Extend export to include dependencies in JSONL

description: Modify export.go to include dependencies array in each issue's JSONL output. This makes JSONL self-contained and enables proper collision resolution. Format: {"id":"bd-10","dependencies":[{"depends_on_id":"bd-5","type":"blocks"}]}

issue_type: task


title: Test issue to verify fix

description: This should be bd-11 if the fix works

status: closed


title: Implement collision detection in import

description: Create collision.go with detectCollisions() function. Compare incoming JSONL issues against DB state. Distinguish between: (1) exact match (idempotent), (2) ID match but different content (collision), (3) new issue. Return list of colliding issues.


title: Implement reference scoring algorithm

description: Count references for each colliding issue: text mentions in descriptions/notes/design fields + dependency references. Sort collisions by score ascending (fewest refs first). This minimizes total updates during renumbering.


title: Implement ID remapping with reference updates

description: Allocate new IDs for colliding issues. Update all text field references using word-boundary regex (\bbd-10\b). Update dependency records. Build id_mapping for reporting. Handle chain dependencies properly.


title: Add --resolve-collisions flag and user reporting

description: Add import flags: --resolve-collisions (auto-fix) and --dry-run (preview). Display clear report: collisions detected, remappings applied (old→new with scores), reference counts updated. Default behavior: fail on collision (safe).


title: Write comprehensive collision resolution tests

description: Test cases: simple collision, multiple collisions, dependency updates, text reference updates, chain dependencies, edge cases (partial ID matches, case sensitivity, triple merges). Add to import_test.go and collision_test.go.


title: Update documentation for collision resolution

description: Update README.md with collision resolution section. Update CLAUDE.md with new workflow. Document --resolve-collisions and --dry-run flags. Add example scenarios showing branch merge workflows.


title: Add design/notes/acceptance_criteria fields to update command

description: Currently bd update only supports status, priority, title, assignee. Add support for --design, --notes, --acceptance-criteria flags. This makes it easier to add detailed designs to issues after creation.


title: Add PostgreSQL backend

description: Implement PostgreSQL storage backend as alternative to SQLite for larger teams


title: Document git workflow in README

description: Add Git Workflow section to README explaining binary vs text approaches

issue_type: chore


title: Add demo GIF/video showing bd quickstart in action

description: Record asciinema or create animated GIF showing the full workflow


title: Implement MCP server for Claude Desktop

description: Complete the claude-desktop-mcp example with working TypeScript implementation


title: Add migration scripts for GitHub Issues

description: Create scripts to import from GitHub Issues API or exported JSON


title: Add performance benchmarks document

description: Document actual performance metrics with hyperfine tests


title: Reach 1.0 release milestone

description: Stabilize API, finalize documentation, comprehensive testing

issue_type: epic


title: Build collision resolution tooling for distributed branch workflows

description: When branches diverge and both create issues, auto-incrementing IDs collide on merge. Build excellent tooling to detect collisions during import, auto-renumber issues with fewer dependencies, update all references in descriptions and dependency links, and provide clear user feedback. Goal: keep beautiful brevity of numeric IDs (bd-302) while handling distributed creation gracefully.