bd init: initialize beads issue tracking
This commit is contained in:
1 parent
0b91a8a2a7
commit
f37c3dce5e
17 files changed
+754
No files matched your search
@@ -0,0 +1,67 @@
|
||||
---
|
||||
alwaysApply: true
|
||||
---
|
||||
|
||||
<!-- BEGIN BEADS INTEGRATION -->
|
||||
<!-- Auto-generated by 'bd setup cursor'. Content between these markers is managed by bd. -->
|
||||
|
||||
# Beads Issue Tracking
|
||||
|
||||
This project uses [Beads (bd)](https://github.com/gastownhall/beads) for issue tracking.
|
||||
|
||||
## Core Rules
|
||||
|
||||
- Track ALL work in bd (never use markdown TODOs or comment-based task lists)
|
||||
- Use `bd ready` to find available work
|
||||
- Use `bd create` to track new issues/tasks/bugs
|
||||
- Treat commit, push, and Dolt remote sync as policy-controlled handoff actions
|
||||
- Run `bd prime` for complete workflow context (SSOT for operational commands)
|
||||
- Default to conservative git authority: report status and proposed commands unless the user, orchestrator, or repository profile explicitly authorizes commit/sync/push
|
||||
|
||||
## Quick Reference
|
||||
|
||||
```bash
|
||||
bd prime # Load complete workflow context (SSOT)
|
||||
bd ready # Show issues ready to work (no blockers)
|
||||
bd list --status=open # List all open issues
|
||||
bd create "title" -t task -p 2 # Create new issue
|
||||
bd update <id> --claim # Claim work atomically
|
||||
bd unclaim <id> # Release stuck issue (agent crashed)
|
||||
bd close <id> # Mark complete
|
||||
bd dep add <issue> <depends-on> # Add dependency
|
||||
bd dolt push # Sync with remote when authorized
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Check for ready work: `bd ready`
|
||||
2. Claim an issue atomically: `bd update <id> --claim`
|
||||
3. Do the work
|
||||
4. Mark complete: `bd close <id>`
|
||||
5. Handoff: report changed files, validation, issue status, and any proposed commit/sync/push commands
|
||||
|
||||
## Issue Types
|
||||
|
||||
- `bug` - Something broken
|
||||
- `feature` - New functionality
|
||||
- `task` - Work item (tests, docs, refactoring)
|
||||
- `epic` - Large feature with subtasks
|
||||
- `chore` - Maintenance (dependencies, tooling)
|
||||
|
||||
## Priorities
|
||||
|
||||
- `0` - Critical (security, data loss, broken builds)
|
||||
- `1` - High (major features, important bugs)
|
||||
- `2` - Medium (default, nice-to-have)
|
||||
- `3` - Low (polish, optimization)
|
||||
- `4` - Backlog (future ideas)
|
||||
|
||||
## Context Loading
|
||||
|
||||
Run `bd prime` to get complete workflow documentation in AI-optimized format.
|
||||
`bd prime` is the single source of truth for operational commands and session workflow.
|
||||
|
||||
For detailed docs: see AGENTS.md, the beads quickstart
|
||||
(https://github.com/gastownhall/beads/blob/main/docs/getting-started/quickstart.md), or run `bd --help`
|
||||
|
||||
<!-- END BEADS INTEGRATION -->
|
||||
Reference in new issue
Block a user