Babysitter issue-tracking

Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/gastown/skills/issue-tracking" ~/.claude/skills/a5c-ai-babysitter-issue-tracking && rm -rf "$T"

manifest: library/methodologies/gastown/skills/issue-tracking/SKILL.md

Issue Tracking

Overview

Track work through Gas Town's bead system: git-backed atomic work units that carry persistent attribution. Each bead is an issue/task with full lifecycle tracking from creation through completion.

When to Use

Creating new beads for a convoy
Tracking bead progress and status
Managing bead dependencies
Collecting attribution data for agent evaluation

Bead Lifecycle

Created: Bead defined with scope and acceptance criteria
Assigned: Bead placed on agent's hook
In Progress: Agent actively working (GUPP enforced)
Review: Work complete, awaiting merge review
Done: Merged and verified (
```
gt done
```
)
Destroyed: Wisps only - cleaned up after landing

Attribution

All work carries persistent attribution:

Which agent completed the bead
Time taken and quality score
Used for A/B testing agent configurations
Feeds into agent evaluation and scoring

Tool Use

Used within convoy management and orchestrator processes.