bd-next

Identify the next beads task by prioritizing the current git branch and load its context.

11|2|Updated Jan 3, 2022
One-click install
npx skills add https://github.com/hay-kot/dotfiles --skill bd-next
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd-next
Source: https://github.com/hay-kot/dotfiles/tree/main/.ai/skills/bd-next
Command: npx skills add https://github.com/hay-kot/dotfiles --skill bd-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers automatically identify and start the next beads task aligned with the current git branch, reducing context switching and speeding up task progression.

Core Features & Use Cases

  • Context-aware task selection: Prioritize in-progress tasks related to the current branch, followed by branch-name matches and ready tasks with no blockers.

  • Context loading: Retrieve full task context with a single command to enable immediate work.

  • Workflow automation: Mark the selected task as in-progress if needed, and begin implementation with a clear starting point.

Quick Start

Identify the next beads task by prioritizing the current branch and load its context for immediate work.

Frequently Asked Questions about bd-next

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

FAQPage Schema
How do I prioritize and load the next beads task for my current git branch?

Prioritize the next beads task by checking your current git branch, searching related in-progress tasks, loading full context, and marking the task as in-progress. This context-aware selection reduces manual searching and accelerates development workflows.

How does branch-based task prioritization work for development workflows?

Branch-based task prioritization works by checking the current git branch and matching it against in-progress tasks, branch-name matches, and ready tasks without blockers. This deterministic process ensures developers automatically select the most relevant task.

Can I automatically mark a beads task as in-progress when starting work?

Yes, the workflow automatically marks the selected beads task as in-progress if needed. After identifying the correct task by branch and loading its context, the status updates immediately to reflect active development.

What is the best way to find the next ready task without blockers in a git workflow?

The best way to find the next ready task is to apply deterministic prioritization: check the current branch, search related in-progress tasks, then evaluate ready tasks with no blockers. This eliminates manual filtering and context switching.

Do I need additional dependencies to automate task selection by branch name?

No additional dependencies are required to automate task selection by branch name. The skill operates independently to check the current branch, search related tasks, and load context directly within your existing development workflow.

Why does task selection prioritize in-progress tasks over ready tasks?

Task selection prioritizes in-progress tasks over ready tasks to minimize context switching and speed up task progression. By finishing partially started work related to the current branch first, developers maintain focus before pulling new ready tasks.