skills.rest
acartine
acartineCOMMUNITY
Explore all skills by this author →
Website𝕏@acartineGitHub

bead_tracking

Automate bead lifecycle tracking with status transitions and PR-based validation.

1|Updated Oct 19, 2025
Search Tags:#git#beads#handoff#pull-request#task-tracking#local-workflow
One-click install
npx skills add https://github.com/acartine/osterman --skill bead-tracking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bead_tracking
Source: https://github.com/acartine/osterman/tree/main/skills/bead_tracking
Command: npx skills add https://github.com/acartine/osterman --skill bead-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provide local, structured task tracking across a project, ensuring every bead from discovery to closure is captured, implemented, and closed with proper handoff.

Core Features & Use Cases

  • Find and claim beads with clear status transitions (ready, in_progress, closed)
  • Implement changes, create PRs, and coordinate with team members via a structured workflow
  • Close beads with a documented reason and handoff notes when work is complete or halted

Quick Start

Instruct the agent to start bead tracking for a specific bead ID.

Frequently Asked Questions about bead_tracking

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

FAQPage Schema
How do I track local micro-tasks from discovery to closure?▼

Structured handoff tracking coordinates local work by enforcing deterministic status transitions across ready, in_progress, and closed states. It captures every micro-task from discovery through implementation to closure using PR-based validation and a STOP/HANDOFF protocol.

How do I enforce task status transitions and pull-request validation in a local workflow?▼

PR-based validation enforces task status transitions by requiring structured handoffs and documented closure reasons before moving a bead from in_progress to closed. It ensures deterministic local-workflow tracking across ready, in_progress, and closed states.

Can I use bead tracking for software projects managing multiple micro-tasks?▼

Bead tracking suits software projects managing multiple micro-tasks with clear status transitions. It operates through a local beads workflow without requiring external dependencies, coordinating team members via structured handoffs and PR-based validation.

What is the STOP/HANDOFF protocol for local task tracking?▼

The STOP/HANDOFF protocol closes beads with documented reasons and handoff notes when work is complete or halted. It enforces structured handoffs within local task tracking, ensuring deterministic phase transitions and proper team coordination.

Best way to manage structured handoffs when halting local development work?▼

Closing beads with documented reasons and handoff notes via the STOP/HANDOFF protocol manages structured handoffs when halting local development work. It enforces proper status updates and coordinates team members during phase transitions.

Related Skills

Explore More Software Engineering Skills→
endlessblinkendlessblink

master-plan-auditor

Audit task status consistency across MASTER_PLAN.md, beads, and git history.

Community
Advanced
vfarcicvfarcic
2

dot-ai-prd-done

Orchestrate PRD implementation workflows with branch management, pull requests, reviews, merges, and issue closure.

Community
Advanced
arakitakashiarakitakashi
1

git-workflow

Standardize Git operations with Git Flow branching and Conventional Commits.

Community
Intermediate
kirvinkirvin

session-close

Save session state to issue notes, push work to repositories, and generate handoff instructions.

Community
Intermediate