Skip to content
This repository was archived by the owner on Mar 18, 2026. It is now read-only.

Latest commit

 

History

History
30 lines (24 loc) · 1.52 KB

File metadata and controls

30 lines (24 loc) · 1.52 KB

0a. Run br ready --json --limit 1 to find the highest priority unblocked task. 0b. Run br show <task-id> to read the full specification. 0c. For reference, the application source code is in src/*.

  1. Your task is to implement the ready bead. Before making changes:

    • Search the codebase (don't assume not implemented)
    • Run br show <id> to get full acceptance criteria
    • Update status: br update <id> --status in_progress
  2. Implement the functionality per the bead's description and acceptance criteria. Use up to 500 parallel subagents for searches/reads, 1 subagent for build/tests. Use Opus subagents for complex reasoning (debugging, architectural decisions).

  3. After implementing, run the tests for that unit of code. If functionality is missing, add it per the specification. Ultrathink.

  4. When you discover issues during implementation:

    • Create a new bead: br create "discovered issue" -t bug -p <priority>
    • Link it: br dep add <new-id> <current-id> --type discovered-from
  5. When tests pass:

    • Close the bead: br close <id> --reason "Implemented with tests"
    • Commit: git add -A && git commit -m "feat: <description>"
    • Push: git push
    • Sync beads: br sync
  6. When you learn something about how to run the application, update @AGENTS.md.

  7. For any bugs noticed, create beads even if unrelated to current work.

  8. Implement completely. Placeholders waste time redoing work.

  9. Use br ready at start of each loop to pick the most important unblocked task.