diff --git a/CLAUDE.md b/CLAUDE.md index 184a91f..c641a2a 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -329,58 +329,14 @@ Covers: **IMPORTANT**: before you do anything else, run the `beans prime` command and heed its output. -## Task Tracking with beans - -`beans` is a CLI tool for managing work tickets (called "beans"), designed for agent workflows. - -### Initialisation +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. ```sh +# Initialise (run once per project directory) 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 -# Update a bean -beans update --json --status in-progress -beans update --json --status completed +# Get full usage guide and instructions for this project +beans prime ``` -### Finding what to work on - -```sh -# All beans that are unblocked and ready to start -beans list --json --ready - -# Filter by type or status -beans list --json --type bug --status todo -``` - -### Workflow - -1. **Before starting** — create a bean: `beans create --json "..." --type task --status todo` -2. **When starting** — mark it in progress: `beans update --json --status in-progress` -3. **When done** — mark it complete: `beans update --json --status completed` - -### Guidelines - -- **Always pass `--json`** to every command for structured, unambiguous output. -- Use `jq` to parse and transform JSON output when needed. -- `--priority` choices: `critical`, `high`, `normal`, `low`, `deferred`. -- `--type` choices: `milestone`, `epic`, `feature`, `task`, `bug`. -- Use `--blocked-by ` to express blockers — beans that must be done first. -- Create beans *before* starting non-trivial tasks, not after. - diff --git a/edu/.claude/skills/work/SKILL.md b/edu/.claude/skills/work/SKILL.md index 035e39a..133948e 100644 --- a/edu/.claude/skills/work/SKILL.md +++ b/edu/.claude/skills/work/SKILL.md @@ -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 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. * Implement the plan in the selected ticket. * Update the ticket with the new status. * Create additional tickets based on work that may have come up during this work. diff --git a/nbd/.claude/skills/triage/SKILL.md b/nbd/.claude/skills/triage/SKILL.md index 4927533..37777c3 100644 --- a/nbd/.claude/skills/triage/SKILL.md +++ b/nbd/.claude/skills/triage/SKILL.md @@ -5,8 +5,8 @@ description: triage issues * Read @docs @src @tests @PLAN.md @README.md and @CLAUDE.md for context before starting. * 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. -* Include relevant source files, documentation, and context about each ticket so the work has the higest 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. -* 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. +* 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 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 bean. +* 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. * Do not implement any tickets. diff --git a/nbd/.claude/skills/work/SKILL.md b/nbd/.claude/skills/work/SKILL.md index 1ee2e5c..dfdbc88 100644 --- a/nbd/.claude/skills/work/SKILL.md +++ b/nbd/.claude/skills/work/SKILL.md @@ -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 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. * Implement the plan in the selected ticket. * Once complete validate changes with cargo fmt, cargo check, cargo clippy, and cargo test. diff --git a/nbd/src/claude_md_snippet.md b/nbd/src/claude_md_snippet.md index 61b4765..5bfc88b 100644 --- a/nbd/src/claude_md_snippet.md +++ b/nbd/src/claude_md_snippet.md @@ -1,54 +1,11 @@ -## Task Tracking with nbd +## Task Tracking with beans -`nbd` is a CLI tool for managing work tickets, designed for agent workflows. - -### Initialisation +This project uses **beans** for issue tracking. Run `beans prime` to get the full usage guide. ```sh -nbd init -``` - -Run once in the project root. Creates `.nbd/tickets/`. Safe to run multiple times. +# Initialise (run once per project directory) +beans init -### Core commands - -```sh -# Create a new ticket (use --ftype md for a human-readable body) -nbd create --title "Add OAuth login" --type feature --priority 7 --ftype md --json - -# List all open tickets (sorted by priority) -nbd list --json - -# Read a specific ticket -nbd read --json - -# Update a ticket -nbd update --status in_progress --json -nbd update --status done --json +# Get full usage guide and instructions for this project +beans prime ``` - -### Finding what to work on - -```sh -# All tickets that are unblocked and ready to start -nbd ready --json - -# The single highest-priority unblocked ticket -nbd next --json -``` - -### Workflow - -1. **Before starting** — create a ticket: `nbd create --title "..." --ftype md --json` -2. **When starting** — mark it in progress: `nbd update --status in_progress --json` -3. **When done** — mark it complete: `nbd update --status done --json` - -### Guidelines - -- **Always pass `--json`** to every command for structured, unambiguous output. -- **Always pass `--ftype md`** when creating tickets — markdown format keeps the body human-readable. -- Use `jq` to parse and transform JSON output when needed. -- Priority scale 0–10: use **7–9** for bugs, **5** for normal tasks, **3** for nice-to-haves. -- `--type` choices: `project`, `feature`, `task`, `bug`. -- Use `--deps id1,id2` to express blockers — tickets that must be done first. -- Create tickets *before* starting non-trivial tasks, not after.