Overview

Issue-tracking for Gas Town beads turns tasks into git-backed, atomic work units with persistent attribution. Each bead represents an issue from creation through completion, enabling lifecycle visibility and reliable provenance. It supports convoy management and orchestrator processes by tracking progress, dependencies, and attribution data.

How This Skill Works

Beads are created with defined scope and acceptance criteria and can be assigned to agents via their hook. The system tracks lifecycle stages (Created, Assigned, In Progress with GUPP, Review, Done, Destroyed) and records attribution data such as the completing agent, duration, and quality score. These beads are git-backed and feed into convoy orchestration and evaluation workflows.

When to Use It

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

Quick Start

1. Step 1: Create a bead with scope and acceptance criteria
2. Step 2: Assign the bead to an agent and start tracking progress
3. Step 3: Complete, review, merge, and mark as Done (or Destroyed when cleanup is needed)

Best Practices

• Define clear scope and acceptance criteria at bead creation
• Use explicit bead dependencies to model task order
• Enforce the In Progress state with GUPP when work starts
• Move beads through Review to Done with merge verification (`gt done`)
• Capture attribution data (agent, time, quality) for evaluation and A/B testing

Example Use Cases

• Bead created for a convoy with scope and criteria
• Bead assigned to an agent's hook
• Bead in Progress under GUPP enforcement
• Bead reviewed and merged, then marked Done
• Post-landing cleanup and Destroyed (Wisps) state

Frequently Asked Questions