a5c-ai/babysitter / library/methodologies/gastown/skills/issue-tracking
issue-tracking
VerifiedTrack beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
SKILL.md
View on GitHub---
name: issue-tracking
description: Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebFetch, WebSearch, Agent, AskUserQuestion
graph:
domains: [domain:software-engineering]
skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]
workflows: [workflow:feature-development]
topics: [topic:developer-experience]
roles: [role:tech-lead, role:backend-engineer]
---
- 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
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |