Skip to content

Latest commit

 

History

History
63 lines (46 loc) · 1.87 KB

AGENTS.md

File metadata and controls

63 lines (46 loc) · 1.87 KB

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd onboard to get started.

🚨 MANDATORY: Session Continuation Protocol

CRITICAL: When this session continues after context compaction/summarization:

YOU MUST IMMEDIATELY RUN:

bd ready

WHY: After context loss, beads is your ONLY source of truth for:

  • What tasks are in progress
  • What was being worked on before context compaction
  • What's blocked/ready to work on
  • Project status and next steps

THIS IS NON-NEGOTIABLE: Do NOT proceed with ANY work until you've run bd ready.

Failure to read beads after context compaction = working blind = wasted effort

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git

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: 
    git pull --rebase
bd sync
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