Simplify all issue-tracking documentation to defer to `beans prime`
rather than maintaining a parallel description of beans commands.
- CLAUDE.md: collapse task-tracking section to just `beans prime` callout
- edu/.claude/skills/work: nbd next → beans list --ready
- nbd/.claude/skills/work: nbd next → beans list --ready
- nbd/.claude/skills/triage: nbd tickets/.nbd → beans beans/.beans
- nbd/src/claude_md_snippet.md: replace nbd snippet with beans prime stub
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
**IMPORTANT**: before you do anything else, run the `beans prime` command and heed its output.
**IMPORTANT**: before you do anything else, run the `beans prime` command and heed its output.
## Task Tracking with beans
This project uses **beans** for issue tracking. `beans prime` outputs the full usage guide for the current project — always follow its instructions for creating, updating, and tracking work.
`beans` is a CLI tool for managing work tickets (called "beans"), designed for agent workflows.
### Initialisation
```sh
```sh
# Initialise (run once per project directory)
beans init
beans init
```
Run once in the project root. Creates `.beans/`. Safe to run multiple times.
### Core commands
```sh
# Create a new bean
beans create --json "Add OAuth login" --type feature --priority high --status todo
# List all beans
beans list --json
# Show a specific bean
beans show --json <id>
# Update a bean
# Get full usage guide and instructions for this project
* Read @docs@src@tests@PLAN.md @README.md and @CLAUDE.md for context before starting.
* Read @docs@src@tests@PLAN.md @README.md and @CLAUDE.md for context before starting.
* Deeply understand each item before planning.
* Deeply understand each item before planning.
* Create `nbd` tickets for each item including your plan, breaking the problem down into smaller tickets where it makes sense.
* Create `beans` beans for each item including your plan, breaking the problem down into smaller beans where it makes sense.
* Include relevant source files, documentation, and context about each ticket so the work has the higest probability of success without additional context being required.
* Include relevant source files, documentation, and context about each bean so the work has the highest probability of success without additional context being required.
* If a file was passed to this skill, remove items from the file which now have a ticket.
* If a file was passed to this skill, remove items from the file which now have a bean.
* Commit these tickets in the `.nbd` directory with a concise summary of each ticket, probably using the title and ticket IDs, and the file passed to this skill if one was passed.
* Commit these beans in the `.beans` directory with a concise summary of each bean, probably using the title and bean IDs, and the file passed to this skill if one was passed.
@ -4,7 +4,7 @@ description: work on the highest priority thing
---
---
* If a ticket ID or description of a ticket is provided, look for that ticket.
* If a ticket ID or description of a ticket is provided, look for that ticket.
* If no ticket/description is provided, use nbd next to choose the ticket to work on.
* If no ticket/description is provided, use `beans list --json --ready` to choose the highest-priority unblocked bean to work on.
* Thoroughly investigate the relevant parts of the codebase to ensure you understand the problem and how to implement the solution as describe in the ticket.
* Thoroughly investigate the relevant parts of the codebase to ensure you understand the problem and how to implement the solution as describe in the ticket.
* Implement the plan in the selected ticket.
* Implement the plan in the selected ticket.
* Once complete validate changes with cargo fmt, cargo check, cargo clippy, and cargo test.
* Once complete validate changes with cargo fmt, cargo check, cargo clippy, and cargo test.
Elijah Voigt
3 months ago