Pick Bean

Update a named bean's status and owner in file and index, creating a feature branch.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/beekeeper-lab/foundry --skill pick-bean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pick Bean
Source: https://github.com/beekeeper-lab/foundry/tree/main/.claude/skills/pick-bean
Command: npx skills add https://github.com/beekeeper-lab/foundry --skill pick-bean

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updates a bean's status from New to Picked (or In Progress) and assigns ownership to the Team Lead, ensuring backlog and bean state stay synchronized.

Core Features & Use Cases

  • Updates the bean.md status and Owner fields, and mirrors changes to the backlog index
  • Validates bean presence, enforces proper status transitions, and provides idempotent behavior for already-owned beans
  • Creates a dedicated feature branch for the bean work and ensures a test integration branch exists

Quick Start

Pick a bean by ID to move it from New to Picked (or In Progress) and assign it to the Team Lead.

Frequently Asked Questions about Pick Bean

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assign backlog items to a team lead and start development?

Backlog item state transitions are validated by checking the current status and enforcing a strict progression from New to Picked or In Progress. This mechanism prevents invalid status changes and ensures ownership is consistently assigned before any development work begins.

How do I create a feature branch when picking up a backlog item?

Creating a feature branch happens automatically when you pick a backlog item by its ID. The process updates the bean file, mirrors the changes to the backlog index, and verifies that a test integration branch exists before assigning ownership to the Team Lead.

What happens if I try to pick a backlog item that is already assigned?

Picking an already-assigned backlog item triggers idempotent behavior, meaning the operation safely recognizes the existing ownership without duplicating the assignment or creating a redundant feature branch. This ensures consistent state transitions even if the command is run multiple times.

Does this backlog assignment workflow require a test integration branch?

Yes, the workflow requires a test integration branch to exist before you can successfully pick a backlog item. The process verifies the branch presence alongside updating the bean file and assigning ownership to the Team Lead to ensure the development environment is ready.

Can I use this tool to manage git workflow transitions for large team backlogs?

You can use this workflow to manage git branching and backlog ownership for teams by enforcing valid state transitions and synchronizing the backlog index with individual bean files. It assigns items to the Team Lead and creates dedicated feature branches to keep development organized.