beads/cmd/bd/@AGENTS.md
coffeegoddd☕️✨ a44d4f9d58 fix(init): replace 'bd onboard' references with 'bd prime' in AGENTS.md (#2902)
bd init creates a complete AGENTS.md but tells users to "Run bd onboard
to get started", which suggests different/conflicting content. Replace
with "Run bd prime" which is the correct entry point for workflow context.

Also migrates the Claude settings prompt from bd onboard to bd prime,
with backward-compatible detection of existing onboard references.

Closes #2902

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-30 10:42:50 -07:00

38 lines
1.3 KiB
Markdown

# Agent Instructions
This project uses **bd** (beads) for issue tracking. Run `bd prime` for full workflow context.
## Quick Reference
```bash
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --claim # Claim work atomically
bd close <id> # Complete work
bd dolt push # Push to Dolt remote
```
## Landing the Plane (Session Completion)
**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.
**MANDATORY WORKFLOW:**
1. **File issues for remaining work** - Create issues for anything that needs follow-up
2. **Run quality gates** (if code changed) - Tests, linters, builds
3. **Update issue status** - Close finished work, update in-progress items
4. **PUSH TO REMOTE** - This is MANDATORY:
```bash
git pull --rebase
git push
git status # MUST show "up to date with origin"
```
5. **Clean up** - Clear stashes, prune remote branches
6. **Verify** - All changes committed AND pushed
7. **Hand off** - Provide context for next session
**CRITICAL RULES:**
- Work is NOT complete until `git push` succeeds
- NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds