tackle

Automate beads issue handling by claiming, scoping, coding, and pushing commits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vonshlovens/vonshlovens --skill tackle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tackle
Source: https://github.com/Vonshlovens/vonshlovens/tree/main/.claude/skills/tackle
Command: npx skills add https://github.com/Vonshlovens/vonshlovens --skill tackle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of handling beads issues by autonomously claiming, scoping, coding, and pushing changes, reducing cycle time and human involvement.

Core Features & Use Cases

  • Autonomous issue handling: Claims, scopes, implements, and pushes commits for beads issues with minimal human input.
  • Context-aware research: Reads descriptions, designs, specs, and notes to inform scoped work before coding.
  • End-to-end workflow: Updates issue status to in_progress or close when criteria are met, and records hand-offs when needed.

Quick Start

Invoke /tackle von-123 to tackle a specific beads issue.

Frequently Asked Questions about tackle

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

FAQPage Schema
How do I automate end-to-end beads issue handling without manual intervention?

Autonomous beads issue handling is achieved by claiming, scoping, coding, and pushing changes without user interaction. The skill reads descriptions, designs, and notes to inform scoped work, then updates issue status to in_progress or closes them when criteria are met.

What is the process for autonomously scoping and coding beads issues?

Autonomous scoping and coding of beads issues involves reading issue details, designs, specs, and notes to inform scoped work before coding. The skill then implements the scoped work and pushes commits with proper notes, updating the issue status throughout the workflow.

Can I use this skill to tackle specific beads issues by issue number?

Yes, you can tackle specific beads issues by invoking the skill with the issue number, such as /tackle von-123. This targets a specific issue for autonomous claiming, scoping, coding, and pushing changes without further user input.

Does autonomous issue management require access to the beads issue tracker?

Yes, autonomous issue management requires access to the beads issue tracker via bd. This access supports reading issue details, updating status to in_progress or closed, implementing scoped work, and pushing commits with proper notes.

How does autonomous coding handle high-priority and in_progress beads issues?

Autonomous coding prioritizes high-priority and in_progress items from the top unblocked issues in the beads workflow. It claims these issues, scopes the work by reading specs and notes, implements the changes, and pushes commits with proper notes.

What are the limitations of autonomous beads issue resolution?

Autonomous beads issue resolution works only with unblocked issues in the beads workflow and requires bd access. It records hand-offs when needed but cannot resolve blocked issues or operate without proper issue tracker connectivity.