# Beads Workflow Guide ## Quick Start ```bash bd ready # Find available work bd show # View issue details bd update --status in_progress # Claim work bd close # Complete work bd sync # Sync with git ``` ## Workflow Commands ### Finding Work - `bd ready` - Show issues ready to work (no blockers) - `bd list --status=open` - All open issues - `bd list --status=in_progress` - Your active work - `bd show ` - Detailed issue view with dependencies ### Creating & Updating - `bd create --title="..." --type=task|bug|feature --priority=2` - New issue - Priority: 0-4 or P0-P4 (0=critical, 2=medium, 4=backlog). NOT "high"/"medium"/"low" - `bd update --status=in_progress` - Claim work - `bd update --assignee=username` - Assign to someone - `bd close ` - Mark complete - `bd close ...` - Close multiple issues at once (more efficient) - `bd close --reason="explanation"` - Close with reason - **Tip**: When creating multiple issues/tasks/epics, use parallel subagents for efficiency ### Dependencies & Blocking - `bd dep add ` - Add dependency (issue depends on depends-on) - `bd blocked` - Show all blocked issues - `bd show ` - See what's blocking/blocked by this issue ### Sync & Collaboration - `bd sync` - Sync with git remote (run at session end) - `bd sync --status` - Check sync status without syncing ### Project Health - `bd stats` - Project statistics (open/closed/blocked counts) - `bd doctor` - Check for issues (sync problems, missing hooks) ## Common Workflows ### Starting Work ```bash bd ready # Find available work bd show # Review issue details bd update --status=in_progress # Claim it ``` ### Completing Work ```bash bd close ... # Close all completed issues at once bd sync # Push to remote ``` ### Creating Dependent Work ```bash # Run bd create commands in parallel (use subagents for many items) bd create --title="Implement feature X" --type=feature bd create --title="Write tests for X" --type=task bd dep add beads-yyy beads-xxx # Tests depend on Feature (Feature blocks tests) ``` ## Integration with Gitea When working on Gitea issues: 1. Create a beads issue to track the work 2. Link to Gitea issue in description or comments 3. When committing, use `Closes #{gitea_number}` to auto-close 4. Close the beads issue after push succeeds ## Session Close Protocol **CRITICAL**: Before saying "done", run this checklist: ``` [ ] 1. git status (check what changed) [ ] 2. git add (stage code changes) [ ] 3. bd sync (commit beads changes) [ ] 4. git commit -m "..." (commit code) [ ] 5. bd sync (commit any new beads changes) [ ] 6. git push (push to remote) ``` Work is NOT complete until `git push` succeeds.