docs(claim): standardize start-work semantics to --claim (#2070)

Standardize start-work semantics to `bd update <id> --claim` across docs,
examples, templates, and website static LLM artifacts. Replaces
`--status in_progress` with `--claim` where the meaning is start-work.

Also fixes stale comment in llms.txt ("Update status" → "Start work").

Co-Authored-By: Valeriy Pavlovich <iqdoctor@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
darcy 2026-02-24 22:11:31 -08:00 • committed by Steve Yegge
commit f9b306f152
46 changed files with 102 additions and 102 deletions

View file

@ -193,7 +193,7 @@ bd update <id> --acceptance "acceptance criteria"
# Make changes (each write auto-commits to Dolt)
bd create "Fix bug" -p 1
bd create "Add tests" -p 1
bd update bd-42 --status in_progress
bd update bd-42 --claim
bd close bd-40 --reason "Completed"
# Push Dolt data to remote if configured

View file

@ -162,7 +162,7 @@ bd q "Task" | xargs bd show # Pipe to other commands
```bash
# Update one or more issues
bd update <id> [<id>...] --status in_progress --json
bd update <id> [<id>...] --claim --json
bd update <id> [<id>...] --priority 1 --json
# Update external reference (v0.9.2+)
@ -630,7 +630,7 @@ bd ready
bd ready --json
# 2. Claim issue
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# 3. Work on it...
@ -672,7 +672,7 @@ bd ready --json # Find work
# During session
bd create "..." -p 1 --json
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# ... work ...
# End of session (IMPORTANT!)

View file

@ -93,7 +93,7 @@ See BOUNDARIES.md for bd vs TodoWrite decision.
"
# Mark in_progress
bd update oauth-1 --status in_progress
bd update oauth-1 --claim
# Create TodoWrite for today's work
TodoWrite:
@ -270,7 +270,7 @@ TESTS: All 12 tests passing (auth, rotation, expiry, error handling)"
1. Create bd issue for tracking:
```bash
bd create "Q4 strategic planning document" -t task -p 0
bd update strat-1 --status in_progress
bd update strat-1 --claim
```
2. Use developing-strategic-documents skill for research and writing

View file

@ -107,7 +107,7 @@ If dependencies still don't persist after updating:
### Symptom
```bash
# In embedded mode, updates may not reflect immediately
bd update issue-1 --status in_progress
bd update issue-1 --claim
bd show issue-1
# Shows: Status: open (not in_progress!)
```
@ -129,14 +129,14 @@ This is **expected behavior** when using embedded mode. Understanding requires k
**Option 1: Use server mode (recommended)**
```bash
# With the Dolt server running, operations reflect immediately
bd update issue-1 --status in_progress
bd update issue-1 --claim
bd show issue-1
# Status reflects immediately
```
**Option 2: Wait for sync (if using embedded mode)**
```bash
bd update issue-1 --status in_progress
bd update issue-1 --claim
# Wait for server to sync
sleep 5
bd show issue-1
@ -145,7 +145,7 @@ bd show issue-1
**Option 3: Manual sync trigger**
```bash
bd update issue-1 --status in_progress
bd update issue-1 --claim
# Trigger sync by exporting/importing
bd export > /dev/null 2>&1 # Forces sync
bd show issue-1

View file

@ -124,7 +124,7 @@ Discovery Workflow:
```
Issue Lifecycle:
- [ ] Start: Update status to in_progress
- [ ] Start: Claim issue with `bd update <id> --claim`
- [ ] During: Add design notes as decisions made
- [ ] During: Update acceptance criteria if requirements clarify
- [ ] During: Add dependencies if blockers discovered
@ -302,7 +302,7 @@ Resume Workflow:
- [ ] List recent closed issues for context
- [ ] Show details on issue to work on
- [ ] Review design notes and acceptance criteria
- [ ] Update status to in_progress
- [ ] Claim issue (`bd update <id> --claim`)
- [ ] Begin work with full context
```
@ -532,7 +532,7 @@ Research or investigation work:
- [ ] Report status to user
- [ ] Get user input on what to work on
- [ ] Show issue details
- [ ] Update to in_progress
- [ ] Claim issue (`bd update <id> --claim`)
- [ ] Begin work
```
@ -620,4 +620,3 @@ Research or investigation work:
2. Use bd ready to focus on unblocked work
3. Consider closing old issues that no longer matter
4. Use labels for organization

View file

@ -77,7 +77,7 @@ SUBCOMMANDS:
fmt.Printf("%s\n", ui.RenderAccent("Quick Examples:"))
fmt.Printf(" %s\n", ui.RenderMuted("# Create and track an issue"))
fmt.Printf(" bd create \"Fix login bug\" --priority 1\n")
fmt.Printf(" bd update bd-abc123 --status in_progress\n")
fmt.Printf(" bd update bd-abc123 --claim\n")
fmt.Printf(" bd close bd-abc123\n\n")
fmt.Printf(" %s\n", ui.RenderMuted("# See what needs doing"))

View file

@ -112,7 +112,7 @@ bd list
bd show <issue-id>
# Update issue status
bd update <issue-id> --status in_progress
bd update <issue-id> --claim
bd update <issue-id> --status done
# Sync with Dolt remote

View file

@ -141,7 +141,7 @@ Use --limit or --range to view specific steps:
fmt.Println(".")
fmt.Println("\nTo start work on a molecule:")
fmt.Println(" bd mol wisp create <proto-id> # Instantiate as ephemeral wisp")
fmt.Println(" bd update <step-id> --status in_progress # Claim a step")
fmt.Println(" bd update <step-id> --claim # Claim a step")
return
}
}
@ -468,7 +468,7 @@ func printMoleculeProgress(mol *MoleculeProgress) {
if mol.NextStep != nil && mol.CurrentStep == nil {
fmt.Printf("\nNext ready: %s - %s\n", mol.NextStep.ID, mol.NextStep.Title)
fmt.Printf(" Start with: bd update %s --status in_progress\n", mol.NextStep.ID)
fmt.Printf(" Start with: bd update %s --claim\n", mol.NextStep.ID)
}
// Show hint about viewing step instructions
@ -599,7 +599,7 @@ func PrintContinueResult(result *ContinueResult) {
if result.AutoAdvanced {
fmt.Printf("\n%s Marked in_progress (use --no-auto to skip)\n", ui.RenderWarn("→"))
} else {
fmt.Printf("\nStart with: bd update %s --status in_progress\n", result.NextStep.ID)
fmt.Printf("\nStart with: bd update %s --claim\n", result.NextStep.ID)
}
}

View file

@ -52,7 +52,7 @@ var quickstartCmd = &cobra.Command{
fmt.Printf(" Perfect for agents to claim next work!\n\n")
fmt.Printf("%s\n", ui.RenderBold("UPDATING ISSUES"))
fmt.Printf(" %s\n", ui.RenderAccent("bd update bd-1 --status in_progress"))
fmt.Printf(" %s\n", ui.RenderAccent("bd update bd-1 --claim"))
fmt.Printf(" %s\n", ui.RenderAccent("bd update bd-1 --priority 0"))
fmt.Printf(" %s\n\n", ui.RenderAccent("bd update bd-1 --assignee bob"))

View file

@ -9,8 +9,8 @@ grep 'Created issue: test-' issue.txt
# Extract ID using grep
exec sh -c 'grep -oE "test-[a-z0-9]+" issue.txt > issue_id.txt'
# Update the issue status
exec sh -c 'bd update $(cat issue_id.txt) --status in_progress'
# Claim the issue (sets status to in_progress)
exec sh -c 'bd update $(cat issue_id.txt) --claim'
stdout 'Updated issue:'
# Verify the update

View file

@ -77,7 +77,7 @@ pipx install aider-chat
You: Let's work on bd-42
Aider: Great choice! To claim it, run:
/run bd update bd-42 --status in_progress
/run bd update bd-42 --claim
```
### During Development
@ -155,7 +155,7 @@ You can customize this file to add project-specific instructions.
/run bd ready
# Claim an issue
/run bd update bd-abc --status in_progress
/run bd update bd-abc --claim
```
### Discovering Work
@ -225,7 +225,7 @@ The AI knows the bd workflow and will suggest appropriate commands:
```
You: I'm starting work on the login feature
Aider: First, let's claim it. Run:
/run bd update bd-xyz --status in_progress
/run bd update bd-xyz --claim
```
### 3. Use bd prime for Context
@ -312,14 +312,14 @@ You: Add the auth files to context and check for related issues
Run multiple bd commands in sequence:
```bash
# In your shell (not aider)
bd ready && bd show bd-42 && bd update bd-42 --status in_progress
bd ready && bd show bd-42 && bd update bd-42 --claim
```
### Integration with Git
Aider handles git commits. bd tracks issues. They work together:
1. Claim issue: `/run bd update bd-42 --status in_progress`
1. Claim issue: `/run bd update bd-42 --claim`
2. Make changes with aider
3. Aider commits changes
4. Complete issue: `/run bd close bd-42`
@ -343,7 +343,7 @@ Aider: Let me check. Run:
You: Let's work on bd-42
Aider: Great! First claim it:
/run bd update bd-42 --status in_progress
/run bd update bd-42 --claim
You: Can you show me the details?

View file

@ -96,7 +96,7 @@ bd create "Jira task" -t task -p 1 --external-ref "jira-PROJ-456" --json # Cust
```bash
# Update one or more issues
bd update <id> [<id>...] --status in_progress --json
bd update <id> [<id>...] --claim --json
bd update <id> [<id>...] --priority 1 --json
bd update <id> [<id>...] --spec-id "docs/specs/auth.md" --json
@ -800,7 +800,7 @@ This makes blocking relationships visible without running `bd show` on each issu
bd ready --json
# 2. Claim issue
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# 3. Work on it...
@ -842,7 +842,7 @@ bd ready --json # Find work
# During session
bd create "..." -p 1 --json
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# ... work ...
# End of session (IMPORTANT!)

View file

@ -109,7 +109,7 @@ EOF
# Do work...
bd create "My issue" -p 1
bd update bd-42 --status in_progress
bd update bd-42 --claim
# Release lock
rm "$LOCK_FILE"

View file

@ -250,7 +250,7 @@ cd ~/work/api && bd ready --json # Uses ~/work/api/.beads/api.db
With Dolt server mode, concurrent writes are handled natively. For distributed setups, Dolt's cell-level merge resolves most conflicts automatically. To prevent conflicts:
- Have agents claim work with `bd update <id> --status in_progress`
- Have agents claim work with `bd update <id> --claim`
- Query by assignee: `bd ready --assignee agent-name`
- Review git diffs before merging
@ -359,9 +359,10 @@ The agent-friendly design works for any AI-assisted workflow.
Yes! Each agent can:
1. Query ready work: `bd ready --assignee agent-name`
2. Claim issues: `bd update <id> --status in_progress --assignee agent-name`
3. Create discovered work: `bd create "Found issue" --deps discovered-from:<parent-id>`
4. Sync via git commits
2. Assign issues: `bd update <id> --assignee agent-name`
3. Start work (as assigned agent): `bd update <id> --claim`
4. Create discovered work: `bd create "Found issue" --deps discovered-from:<parent-id>`
5. Sync via git commits
bd's git-based sync means agents work independently and merge their changes like developers do.

View file

@ -55,7 +55,7 @@ bd config set sync.branch beads-sync
```bash
# Agents work normally - no changes needed!
bd create "Fix authentication" -t bug -p 1
bd update bd-a1b2 --status in_progress
bd update bd-a1b2 --claim
bd close bd-a1b2 "Fixed"
```

View file

@ -226,7 +226,7 @@ bd list --label needs-triage
### Quality Gate Workflow
```bash
# Start work
bd update bd-42 --status in_progress
bd update bd-42 --claim
# Mark quality requirements
bd label add bd-42 needs-tests
@ -426,7 +426,7 @@ bd create "Extract validateToken function" -t chore -p 2 \
--deps discovered-from:bd-10
# Agent marks work for review
bd update bd-42 --status in_progress
bd update bd-42 --claim
# ... agent does work ...
bd label add bd-42 needs-review
bd label add bd-42 ai-generated

View file

@ -56,7 +56,7 @@ bd dep add <B-id> <A-id> # B depends on A (B needs A)
An agent works through a molecule by:
1. Getting ready work (`bd ready`)
2. Claiming it (`bd update <id> --status in_progress`)
2. Claiming it (`bd update <id> --claim`)
3. Doing the work
4. Closing it (`bd close <id>`)
5. Repeat until molecule is done
@ -259,7 +259,7 @@ Issues (Dolt, version-controlled) ← STORAGE
```bash
bd ready # What's ready to work
bd blocked # What's blocked
bd update <id> --status in_progress
bd update <id> --claim
bd close <id>
```

View file

@ -136,7 +136,7 @@ bd ready
bd list --json
# Work on an issue
bd update plan-42 --status in_progress
bd update plan-42 --claim
# Complete work
bd close plan-42 --reason "Completed"

View file

@ -195,7 +195,7 @@ AI agents work exactly the same way as before:
bd create "Implement user authentication" -t feature -p 1
# Update issues
bd update bd-a1b2 --status in_progress
bd update bd-a1b2 --claim
# Close issues
bd close bd-a1b2 "Completed authentication"

View file

@ -166,7 +166,7 @@ Only bd-1 is ready because bd-2 and bd-3 are blocked!
```bash
# Start working on bd-1
./bd update bd-1 --status in_progress
./bd update bd-1 --claim
# Complete it
./bd close bd-1 --reason "Database setup complete"

View file

@ -400,7 +400,7 @@ Aider: Let me check. Run:
You: [runs the command]
Aider: Great! To claim bd-42, run:
/run bd update bd-42 --status in_progress
/run bd update bd-42 --claim
```
This respects Aider's philosophy of keeping humans in control while still leveraging beads for issue tracking.

View file

@ -718,7 +718,7 @@ When auto-detected, you'll see: `ℹ️ Sandbox detected, using direct mode`
# Explicitly enable sandbox mode
bd --sandbox ready
bd --sandbox create "Fix bug" -p 1
bd --sandbox update bd-42 --status in_progress
bd --sandbox update bd-42 --claim
```
**What sandbox mode does:**

View file

@ -144,7 +144,7 @@ bd config set sync-branch beads-sync
# Now server mode works safely in all worktrees
cd feature-worktree
bd create "Implement feature X" -t feature -p 1
bd update bd-a1b2 --status in_progress
bd update bd-a1b2 --claim
bd ready # Auto-syncs to beads-sync branch
```

View file

@ -46,7 +46,7 @@ cd git-hooks
The basic agent workflow:
1. **Find ready work**: `bd ready --json --limit 1`
2. **Claim the task**: `bd update <id> --status in_progress --json`
2. **Claim the task**: `bd update <id> --claim --json`
3. **Do the work**: Execute the task
4. **Discover new issues**: `bd create "Found bug" --json`
5. **Link discoveries**: `bd dep add <new-id> <parent-id> --type discovered-from`

View file

@ -67,7 +67,7 @@ claim_task() {
local issue_id="$1"
log_info "Claiming task: $issue_id"
bd update "$issue_id" --status in_progress --json > /dev/null
bd update "$issue_id" --claim --json > /dev/null
log_success "Task claimed"
return 0

View file

@ -282,7 +282,7 @@ Regular synchronization:
bd linear sync --pull
# Do local work
bd update bd-123 --status in_progress
bd update bd-123 --claim
# ... work ...
bd close bd-123 --reason "Fixed"

View file

@ -96,7 +96,7 @@ bd create "Build simple UI for testing" -p 2 \
--deps discovered-from:bd-a1b2c3.2
# Start implementing
bd update bd-xyz --status in_progress
bd update bd-xyz --claim
```
### Discovered Work During MVP
@ -272,7 +272,7 @@ bd dep add bd-a1b2.4 bd-a1b2.3 --type blocks
# Week 1: Phase 1 (Research)
bd ready # Shows Phase 1 tasks
bd create "Compare Auth0 vs Firebase" -p 1 --deps discovered-from:bd-a1b2.1
bd update bd-xyz --status in_progress
bd update bd-xyz --claim
# ... research complete ...
bd close bd-a1b2.1 --reason "Chose Auth0"

View file

@ -117,7 +117,7 @@ bd list --label implementation --type bug --priority 1
```bash
# Claim a task
bd update bd-impl1 --status in_progress
bd update bd-impl1 --claim
# During implementation, discover issues
bd create "Need connection retry logic" -t bug -p 1 \
@ -166,7 +166,7 @@ bd list --label review --priority 1
```bash
# Claim review
bd update bd-review1 --status in_progress
bd update bd-review1 --claim
# Found issues during review
bd create "Add unit tests for retry logic" -t task -p 1 \
@ -259,7 +259,7 @@ bd create "Research rate limiting algorithms" -p 1 \
--deps discovered-from:bd-epic1
bd label add bd-research1 architecture research
bd update bd-research1 --status in_progress
bd update bd-research1 --claim
# ... research done ...
bd close bd-research1 --reason "Chose token bucket algorithm"
@ -290,7 +290,7 @@ bd create "Add rate limit middleware" -p 1 \
bd label add bd-impl2 implementation
# Claim and start
bd update bd-impl1 --status in_progress
bd update bd-impl1 --claim
# Discover issues
bd create "Need distributed rate limiting (Redis)" -t bug -p 1 \
@ -340,7 +340,7 @@ bd label add bd-review1 review
bd dep add bd-review1 bd-impl1 --type related
bd dep add bd-review1 bd-impl3 --type related
bd update bd-review1 --status in_progress
bd update bd-review1 --claim
# Found issues
bd create "Add integration tests for Redis" -t task -p 1 \
@ -360,10 +360,10 @@ bd dep add bd-review1 bd-bug2 --type blocks
```bash
# Fix review findings
bd update bd-bug2 --status in_progress
bd update bd-bug2 --claim
bd close bd-bug2 --reason "Added circuit breaker for Redis"
bd update bd-test1 --status in_progress
bd update bd-test1 --claim
bd close bd-test1 --reason "Integration tests passing"
```
@ -608,7 +608,7 @@ bd create "App crashes on large files" -t bug -p 1
# Implementer investigates
bd update bd-bug1 --label implementation
bd update bd-bug1 --status in_progress
bd update bd-bug1 --claim
# Discovers architectural issue
bd create "Need streaming uploads, not buffering" -t bug -p 0
@ -620,7 +620,7 @@ bd update bd-arch1 --label architecture
bd close bd-arch1 --reason "Designed streaming upload flow"
# Implementer fixes
bd update bd-bug1 --status in_progress
bd update bd-bug1 --claim
bd close bd-bug1 --reason "Implemented streaming uploads"
```

View file

@ -43,7 +43,7 @@ bd link bd-XXXXX --blocks bd-YYYYY # auth blocks login
bd link bd-XXXXX --blocks bd-ZZZZZ # auth blocks tests
# Start work
bd update bd-XXXXX --status in_progress
bd update bd-XXXXX --claim
```
**Note:** Replace `bd-XXXXX` etc. with actual issue IDs created above.

View file

@ -133,7 +133,7 @@ git pull
bd list # Sees Alice's issue
# Bob claims it
bd update bd-abc --status in_progress
bd update bd-abc --claim
# Auto-commits Bob's update
# Alice pulls and sees Bob is working on it
@ -197,7 +197,7 @@ bd dep add bd-def bd-abc --type blocks
bd create "Refactor auth module" -p 1
# Work on it
bd update bd-abc --status in_progress
bd update bd-abc --claim
# Open PR with issue reference
git push origin feature-branch

View file

@ -94,8 +94,8 @@ bd create "Fix authentication bug" -t bug -p 1
# View ready work
bd ready
# Update status
bd update bd-a1b2 --status in_progress
# Start work
bd update bd-a1b2 --claim
# Add dependencies
bd dep add bd-f14c bd-a1b2
@ -115,7 +115,7 @@ Use the `bd` command for all issue tracking instead of markdown TODOs:
- Create issues: `bd create "Task description" -p 1 --json`
- Find work: `bd ready --json`
- Update status: `bd update <id> --status in_progress --json`
- Start work: `bd update <id> --claim --json`
- View details: `bd show <id> --json`
Use `--json` flags for programmatic parsing.
@ -296,7 +296,7 @@ You are working on a project that uses bd (beads) for issue tracking.
At the start of each session:
1. Run `bd ready --json` to see available work
2. Choose an issue to work on
3. Update its status: `bd update <id> --status in_progress`
3. Start work: `bd update <id> --claim`
While working:
- Create new issues for any bugs you discover

View file

@ -73,8 +73,8 @@ bd create "Bug description" -t bug -p 0 --json
### Working on Issues
```bash
# Update status to in_progress
bd update <issue-id> --status in_progress
# Start work (atomic claim)
bd update <issue-id> --claim
# Add a comment
bd comments add <issue-id> "Progress update"
@ -146,7 +146,7 @@ System: bd-a1b2 [P1] Fix authentication bug
System: bd-f14c [P1] Add user profile page
System:
Agent: I can see there are 2 ready tasks. Let me work on bd-a1b2 (Fix authentication bug).
Agent: [runs] bd update bd-a1b2 --status in_progress
Agent: [runs] bd update bd-a1b2 --claim
```
### Pattern 2: Discovering New Work
@ -314,7 +314,7 @@ You have access to bd (beads) for issue tracking. It's automatically installed i
WORKFLOW:
1. Start each session: Check `bd ready --json` for available work
2. Choose a task: Pick highest priority with no blockers
3. Update status: `bd update <id> --status in_progress`
3. Start work: `bd update <id> --claim`
4. Work on it: Implement, test, document
5. File new issues: Create issues for any work discovered
6. Link issues: Use `bd dep add` to track relationships

View file

@ -65,8 +65,8 @@ bd show bd-a1b2
# List all issues
bd list --json
# Update status
bd update bd-a1b2 --status in_progress
# Start work
bd update bd-a1b2 --claim
# Add dependency
bd dep add bd-f14c bd-a1b2

View file

@ -223,7 +223,7 @@ async function testBasicWorkflow(npmPrefix) {
// Test bd update
logInfo('Testing bd update...');
exec(`"${bdCmd}" update ${issue.id} --status in_progress`, { cwd: projectDir, env });
exec(`"${bdCmd}" update ${issue.id} --claim`, { cwd: projectDir, env });
const updatedOutput = exec(`"${bdCmd}" show ${issue.id} --json`, { cwd: projectDir, env });
const updatedResult = JSON.parse(updatedOutput);
const updatedIssue = Array.isArray(updatedResult) ? updatedResult[0] : updatedResult;

View file

@ -96,7 +96,7 @@ bd update <id> [flags]
**Examples:**
```bash
bd update bd-42 --status in_progress
bd update bd-42 --claim
bd update bd-42 --priority 0 --add-label urgent
bd update bd-42 --title "Updated title" --json
```

View file

@ -105,7 +105,7 @@ bd update <id> [flags]
**Examples:**
```bash
# Start work
bd update bd-42 --status in_progress
bd update bd-42 --claim
# Escalate priority
bd update bd-42 --priority 0 --add-label urgent
@ -114,7 +114,7 @@ bd update bd-42 --priority 0 --add-label urgent
bd update bd-42 --title "New title" --description="Updated description"
# Multiple changes
bd update bd-42 --status in_progress --priority 1 --add-label "in-review" --json
bd update bd-42 --claim --priority 1 --add-label "in-review" --json
```
## bd close

View file

@ -134,7 +134,7 @@ bd dep tree bd-a3f8e9
```bash
# Change status
bd update bd-42 --status in_progress
bd update bd-42 --claim
# Change priority
bd update bd-42 --priority 0
@ -143,7 +143,7 @@ bd update bd-42 --priority 0
bd update bd-42 --add-label urgent
# Multiple changes
bd update bd-42 --status in_progress --priority 1 --add-label "in-review"
bd update bd-42 --claim --priority 1 --add-label "in-review"
```
## Closing Issues

View file

@ -122,7 +122,7 @@ Only bd-1 is ready because bd-2 and bd-3 are blocked!
```bash
# Start working on bd-1
bd update bd-1 --status in_progress
bd update bd-1 --claim
# Complete it
bd close bd-1 --reason "Database setup complete"

View file

@ -52,7 +52,7 @@ Use bd commands alongside aider:
```bash
# In another terminal or after exiting aider
bd create "Found bug during work" --deps discovered-from:bd-42 --json
bd update bd-42 --status in_progress
bd update bd-42 --claim
bd ready
```

View file

@ -69,7 +69,7 @@ bd create "Found SQL injection" \
bd ready --json
# Start work
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# Complete work
bd close bd-42 --reason "Fixed in commit abc123" --json

View file

@ -99,7 +99,7 @@ bd create "Found SQL injection" \
bd ready --json
# Start work
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# Complete work
bd close bd-42 --reason "Fixed in commit abc123" --json

View file

@ -51,7 +51,7 @@ bd pin bd-42 --for agent-b
# Agent B picks up
bd hook # Sees bd-42
bd update bd-42 --status in_progress
bd update bd-42 --claim
```
### Parallel Work

View file

@ -81,7 +81,7 @@ bd pour release --var version=1.0.0
bd mol show release-1.0.0
# Work through steps
bd update release-1.0.0.1 --status in_progress
bd update release-1.0.0.1 --claim
bd close release-1.0.0.1
# Next step becomes ready...
```

View file

@ -70,7 +70,7 @@ bd ready # Only shows steps with completed dependencies
```bash
# Start a step
bd update bd-xyz.1 --status in_progress
bd update bd-xyz.1 --claim
# Complete a step
bd close bd-xyz.1 --reason "Done"
@ -150,7 +150,7 @@ bd pour feature-workflow --var name="dark-mode"
bd dep tree bd-xyz
# 3. Start first step
bd update bd-xyz.1 --status in_progress
bd update bd-xyz.1 --claim
# 4. Complete and progress
bd close bd-xyz.1

View file

@ -684,7 +684,7 @@ Only bd-1 is ready because bd-2 and bd-3 are blocked!
```bash
# Start working on bd-1
bd update bd-1 --status in_progress
bd update bd-1 --claim
# Complete it
bd close bd-1 --reason "Database setup complete"
@ -1188,7 +1188,7 @@ bd dep tree bd-a3f8e9
```bash
# Change status
bd update bd-42 --status in_progress
bd update bd-42 --claim
# Change priority
bd update bd-42 --priority 0
@ -1197,7 +1197,7 @@ bd update bd-42 --priority 0
bd update bd-42 --add-label urgent
# Multiple changes
bd update bd-42 --status in_progress --priority 1 --add-label "in-review"
bd update bd-42 --claim --priority 1 --add-label "in-review"
```
## Closing Issues
@ -2043,7 +2043,7 @@ bd update <id> [flags]
**Examples:**
```bash
bd update bd-42 --status in_progress
bd update bd-42 --claim
bd update bd-42 --priority 0 --add-label urgent
bd update bd-42 --title "Updated title" --json
```
@ -2267,7 +2267,7 @@ bd update <id> [flags]
**Examples:**
```bash
# Start work
bd update bd-42 --status in_progress
bd update bd-42 --claim
# Escalate priority
bd update bd-42 --priority 0 --add-label urgent
@ -2276,7 +2276,7 @@ bd update bd-42 --priority 0 --add-label urgent
bd update bd-42 --title "New title" --description="Updated description"
# Multiple changes
bd update bd-42 --status in_progress --priority 1 --add-label "in-review" --json
bd update bd-42 --claim --priority 1 --add-label "in-review" --json
```
## bd close
@ -2819,7 +2819,7 @@ bd pour release --var version=1.0.0
bd mol show release-1.0.0
# Work through steps
bd update release-1.0.0.1 --status in_progress
bd update release-1.0.0.1 --claim
bd close release-1.0.0.1
# Next step becomes ready...
```
@ -3370,7 +3370,7 @@ bd ready # Only shows steps with completed dependencies
```bash
# Start a step
bd update bd-xyz.1 --status in_progress
bd update bd-xyz.1 --claim
# Complete a step
bd close bd-xyz.1 --reason "Done"
@ -3450,7 +3450,7 @@ bd pour feature-workflow --var name="dark-mode"
bd dep tree bd-xyz
# 3. Start first step
bd update bd-xyz.1 --status in_progress
bd update bd-xyz.1 --claim
# 4. Complete and progress
bd close bd-xyz.1
@ -3718,7 +3718,7 @@ bd pin bd-42 --for agent-b
# Agent B picks up
bd hook # Sees bd-42
bd update bd-42 --status in_progress
bd update bd-42 --claim
```
### Parallel Work
@ -3996,7 +3996,7 @@ Use bd commands alongside aider:
```bash
# In another terminal or after exiting aider
bd create "Found bug during work" --deps discovered-from:bd-42 --json
bd update bd-42 --status in_progress
bd update bd-42 --claim
bd ready
```
@ -4129,7 +4129,7 @@ bd create "Found SQL injection" \
bd ready --json
# Start work
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# Complete work
bd close bd-42 --reason "Fixed in commit abc123" --json
@ -4489,7 +4489,7 @@ bd create "Found SQL injection" \
bd ready --json
# Start work
bd update bd-42 --status in_progress --json
bd update bd-42 --claim --json
# Complete work
bd close bd-42 --reason "Fixed in commit abc123" --json

View file

@ -21,7 +21,7 @@ cd your-project && bd init --quiet
bd create "Title" -t bug -p 1 --json # Create issue
bd list --status open --json # List issues
bd show bd-42 --json # Show details
bd update bd-42 --status in_progress # Update status
bd update bd-42 --claim # Start work
bd close bd-42 --reason "Done" # Close issue
bd ready --json # Show unblocked work
bd sync # Sync to git