issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
Best use case
issue-tracking is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
Teams using issue-tracking should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/issue-tracking/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How issue-tracking Compares
| Feature / Agent | issue-tracking | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
issue
Run an issue-centric Babysitter workflow.
issue-tracker
Track and manage project issues with escalation and resolution workflows
benefits-tracking-dashboard
Track and visualize benefit realization against targets
brand-tracking
Brand health measurement and tracking platform integration
issue-tree-generator
Generate and validate issue trees for structured problem solving with MECE validation
Progress Tracking
Status dashboards, standup reports, and blocked task management with GitHub synchronization.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.