issue-tracking
The issue-tracking skill enables tracking of discrete work units called beads within Gas Town's git-backed system, maintaining persistent attribution for each completed task throughout its lifecycle from creation to completion. Use this skill when creating new work items for a convoy, monitoring bead progress and status, managing task dependencies, or collecting attribution data for evaluating agent performance and quality metrics.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/issue-tracking && cp -r /tmp/issue-tracking/library/methodologies/gastown/skills/issue-tracking ~/.claude/skills/issue-trackingSKILL.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 1. **Created**: Bead defined with scope and acceptance criteria 2. **Assigned**: Bead placed on agent's hook 3. **In Progress**: Agent actively working (GUPP enforced) 4. **Review**: Work complete, awaiting merge review 5. **Done**: Merged and verified (`gt done`) 6. **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.
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement