{"owner":"gastownhall","repo":"gastown","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Agent Instructions\n\nSee **CLAUDE.md** for complete agent context and instructions.\n\nThis file exists for compatibility with tools that look for AGENTS.md.\n\n> **Recovery**: Run `gt prime` after compaction, clear, or new session\n\nFull context is injected by `gt prime` at session start.\n\n<!-- beads-agent-instructions-v2 -->\n\n---\n\n## Beads Workflow Integration\n\nThis project uses [beads](https://github.com/steveyegge/beads) for issue tracking. Issues live in `.beads/` and are tracked in git.\n\nTwo CLIs: **bd** (issue CRUD) and **bv** (graph-aware triage, read-only).\n\n### bd: Issue Management\n\n```bash\nbd ready              # Unblocked issues ready to work\nbd list --status=open # All open issues\nbd show <id>          # Full details with dependencies\nbd create --title=\"...\" --type=task --priority=2\nbd update <id> --status=in_progress\nbd close <id>         # Mark complete\nbd close <id1> <id2>  # Close multiple\nbd dep add <a> <b>    # a depends on b\nbd sync               # Sync with git\n```\n\n### bv: Graph Analysis (read-only)\n\n**NEVER run bare `bv`** — it launches interactive TUI. Always use `--robot-*` flags:\n\n```bash\nbv --robot-triage     # Ranked picks, quick wins, blockers, health\nbv --robot-next       # Single top pick + claim command\nbv --robot-plan       # Parallel execution tracks\nbv --robot-alerts     # Stale issues, cascades, mismatches\nbv --robot-insights   # Full graph metrics: PageRank, betweenness, cycles\n```\n\n### Workflow\n\n1. **Start**: `bd ready` (or `bv --robot-triage` for graph analysis)\n2. **Claim**: `bd update <id> --status=in_progress`\n3. **Work**: Implement the task\n4. **Complete**: `bd close <id>`\n5. **Sync**: `bd sync` at session end\n\n### Session Close Protocol\n\n```bash\ngit status            # Check what changed\ngit add <files>       # Stage code changes\nbd sync               # Commit beads changes\ngit commit -m \"...\"   # Commit code\nbd sync               # Commit any new beads changes\ngit push              # Push to remote\n```\n\n### Key Concepts\n\n- **Priority**: P0=critical, P1=high, P2=medium, P3=low, P4=backlog (numbers only)\n- **Types**: task, bug, feature, epic, question, docs\n- **Dependencies**: `bd ready` shows only unblocked work\n\n<!-- end-beads-agent-instructions -->\n\n<!-- gastown-agent-instructions-v1 -->\n\n---\n\n## Gas Town Multi-Agent Communication\n\nThis workspace is part of a **Gas Town** multi-agent environment. You communicate\nwith other agents using `gt` commands — never by printing text or using raw tmux.\n\n### Nudging Agents (Immediate Delivery)\n\n`gt nudge` sends a message directly to another agent's active session:\n\n```bash\ngt nudge mayor \"Status update: PR review complete\"\ngt nudge laneassist/crew/dom \"Check your mail — PR ready for review\"\ngt nudge witness \"Polecat health check needed\"\ngt nudge refinery \"Merge queue has items\"\n```\n\n**Target formats:**\n- Role shortcuts: `mayor`, `deacon`, `witness`, `refinery`\n- Full path: `<rig>/crew/<name>`, `<rig>/polecats/<name>`\n\n**Important:** `gt nudge` is the ONLY way to send text to another agent's session.\nNever print \"Hey @name\" — the other agent cannot see your terminal output.\n\n### Sending Mail (Persistent Messages)\n\n`gt mail` sends messages that persist across session restarts:\n\n```bash\n# Reading\ngt mail inbox                    # List messages\ngt mail read <id>                # Read a specific message\n\n# Sending (use --stdin for multi-line content)\ngt mail send mayor/ -s \"Subject\" -m \"Short message\"\ngt mail send laneassist/crew/dom -s \"PR Review\" --stdin <<'BODY'\nMulti-line message content here.\nDetails about the PR and what to look for.\nBODY\ngt mail send --human -s \"Subject\" -m \"Message to overseer\"\n```\n\n### When to Use Which\n\n| Want to... | Command | Why |\n|------------|---------|-----|\n| Wake a sleeping agent | `gt nudge <target> \"msg\"` | Immediate delivery |\n| Send detailed task/info | `gt mail send <target> -s \"...\" --stdin` | Persists across restarts |\n| Both: send + wake | `gt mail send` then `gt nudge` | Mail carries payload, nudge wakes |\n\n### Context Recovery\n\nAfter compaction or new session, run `gt prime` to reload your full role context,\nidentity, and any pending work.\n\n```bash\ngt prime              # Full context reload\ngt hook               # Check for assigned work\ngt mail inbox         # Check for messages\n```\n\n<!-- end-gastown-agent-instructions -->\n\n<!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:ca08a54f -->\n## Beads Issue Tracker\n\nThis project uses **bd (beads)** for issue tracking. Run `gt prime` to see full workflow context and commands.\n\n### Quick Reference\n\n```bash\nbd ready              # Find available work\nbd show <id>          # View issue details\nbd update <id> --claim  # Claim work\nbd close <id>         # Complete work\n```\n\n### Rules\n\n- Use `bd` for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists\n- Run `gt prime` for detailed command reference and session close protocol\n- Use `bd remember` for persistent knowledge — do NOT use MEMORY.md files\n\n## Session Completion\n\n**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.\n\n**MANDATORY WORKFLOW:**\n\n1. **File issues for remaining work** - Create issues for anything that needs follow-up\n2. **Run quality gates** (if code changed) - Tests, linters, builds\n3. **Update issue status** - Close finished work, update in-progress items\n4. **PUSH TO REMOTE** - This is MANDATORY:\n   ```bash\n   git pull --rebase\n   bd dolt push\n   git push\n   git status  # MUST show \"up to date with origin\"\n   ```\n5. **Clean up** - Clear stashes, prune remote branches\n6. **Verify** - All changes committed AND pushed\n7. **Hand off** - Provide context for next session\n\n**CRITICAL RULES:**\n- Work is NOT complete until `git push` succeeds\n- NEVER stop before pushing - that leaves work stranded locally\n- NEVER say \"ready to push when you are\" - YOU must push\n- If push fails, resolve and retry until it succeeds\n<!-- END BEADS INTEGRATION -->\n"},"files":{"AGENTS.md":"# Agent Instructions\n\nSee **CLAUDE.md** for complete agent context and instructions.\n\nThis file exists for compatibility with tools that look for AGENTS.md.\n\n> **Recovery**: Run `gt prime` after compaction, clear, or new session\n\nFull context is injected by `gt prime` at session start.\n\n<!-- beads-agent-instructions-v2 -->\n\n---\n\n## Beads Workflow Integration\n\nThis project uses [beads](https://github.com/steveyegge/beads) for issue tracking. Issues live in `.beads/` and are tracked in git.\n\nTwo CLIs: **bd** (issue CRUD) and **bv** (graph-aware triage, read-only).\n\n### bd: Issue Management\n\n```bash\nbd ready              # Unblocked issues ready to work\nbd list --status=open # All open issues\nbd show <id>          # Full details with dependencies\nbd create --title=\"...\" --type=task --priority=2\nbd update <id> --status=in_progress\nbd close <id>         # Mark complete\nbd close <id1> <id2>  # Close multiple\nbd dep add <a> <b>    # a depends on b\nbd sync               # Sync with git\n```\n\n### bv: Graph Analysis (read-only)\n\n**NEVER run bare `bv`** — it launches interactive TUI. Always use `--robot-*` flags:\n\n```bash\nbv --robot-triage     # Ranked picks, quick wins, blockers, health\nbv --robot-next       # Single top pick + claim command\nbv --robot-plan       # Parallel execution tracks\nbv --robot-alerts     # Stale issues, cascades, mismatches\nbv --robot-insights   # Full graph metrics: PageRank, betweenness, cycles\n```\n\n### Workflow\n\n1. **Start**: `bd ready` (or `bv --robot-triage` for graph analysis)\n2. **Claim**: `bd update <id> --status=in_progress`\n3. **Work**: Implement the task\n4. **Complete**: `bd close <id>`\n5. **Sync**: `bd sync` at session end\n\n### Session Close Protocol\n\n```bash\ngit status            # Check what changed\ngit add <files>       # Stage code changes\nbd sync               # Commit beads changes\ngit commit -m \"...\"   # Commit code\nbd sync               # Commit any new beads changes\ngit push              # Push to remote\n```\n\n### Key Concepts\n\n- **Priority**: P0=critical, P1=high, P2=medium, P3=low, P4=backlog (numbers only)\n- **Types**: task, bug, feature, epic, question, docs\n- **Dependencies**: `bd ready` shows only unblocked work\n\n<!-- end-beads-agent-instructions -->\n\n<!-- gastown-agent-instructions-v1 -->\n\n---\n\n## Gas Town Multi-Agent Communication\n\nThis workspace is part of a **Gas Town** multi-agent environment. You communicate\nwith other agents using `gt` commands — never by printing text or using raw tmux.\n\n### Nudging Agents (Immediate Delivery)\n\n`gt nudge` sends a message directly to another agent's active session:\n\n```bash\ngt nudge mayor \"Status update: PR review complete\"\ngt nudge laneassist/crew/dom \"Check your mail — PR ready for review\"\ngt nudge witness \"Polecat health check needed\"\ngt nudge refinery \"Merge queue has items\"\n```\n\n**Target formats:**\n- Role shortcuts: `mayor`, `deacon`, `witness`, `refinery`\n- Full path: `<rig>/crew/<name>`, `<rig>/polecats/<name>`\n\n**Important:** `gt nudge` is the ONLY way to send text to another agent's session.\nNever print \"Hey @name\" — the other agent cannot see your terminal output.\n\n### Sending Mail (Persistent Messages)\n\n`gt mail` sends messages that persist across session restarts:\n\n```bash\n# Reading\ngt mail inbox                    # List messages\ngt mail read <id>                # Read a specific message\n\n# Sending (use --stdin for multi-line content)\ngt mail send mayor/ -s \"Subject\" -m \"Short message\"\ngt mail send laneassist/crew/dom -s \"PR Review\" --stdin <<'BODY'\nMulti-line message content here.\nDetails about the PR and what to look for.\nBODY\ngt mail send --human -s \"Subject\" -m \"Message to overseer\"\n```\n\n### When to Use Which\n\n| Want to... | Command | Why |\n|------------|---------|-----|\n| Wake a sleeping agent | `gt nudge <target> \"msg\"` | Immediate delivery |\n| Send detailed task/info | `gt mail send <target> -s \"...\" --stdin` | Persists across restarts |\n| Both: send + wake | `gt mail send` then `gt nudge` | Mail carries payload, nudge wakes |\n\n### Context Recovery\n\nAfter compaction or new session, run `gt prime` to reload your full role context,\nidentity, and any pending work.\n\n```bash\ngt prime              # Full context reload\ngt hook               # Check for assigned work\ngt mail inbox         # Check for messages\n```\n\n<!-- end-gastown-agent-instructions -->\n\n<!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:ca08a54f -->\n## Beads Issue Tracker\n\nThis project uses **bd (beads)** for issue tracking. Run `gt prime` to see full workflow context and commands.\n\n### Quick Reference\n\n```bash\nbd ready              # Find available work\nbd show <id>          # View issue details\nbd update <id> --claim  # Claim work\nbd close <id>         # Complete work\n```\n\n### Rules\n\n- Use `bd` for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists\n- Run `gt prime` for detailed command reference and session close protocol\n- Use `bd remember` for persistent knowledge — do NOT use MEMORY.md files\n\n## Session Completion\n\n**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.\n\n**MANDATORY WORKFLOW:**\n\n1. **File issues for remaining work** - Create issues for anything that needs follow-up\n2. **Run quality gates** (if code changed) - Tests, linters, builds\n3. **Update issue status** - Close finished work, update in-progress items\n4. **PUSH TO REMOTE** - This is MANDATORY:\n   ```bash\n   git pull --rebase\n   bd dolt push\n   git push\n   git status  # MUST show \"up to date with origin\"\n   ```\n5. **Clean up** - Clear stashes, prune remote branches\n6. **Verify** - All changes committed AND pushed\n7. **Hand off** - Provide context for next session\n\n**CRITICAL RULES:**\n- Work is NOT complete until `git push` succeeds\n- NEVER stop before pushing - that leaves work stranded locally\n- NEVER say \"ready to push when you are\" - YOU must push\n- If push fails, resolve and retry until it succeeds\n<!-- END BEADS INTEGRATION -->\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Agent Instructions\n\nSee **CLAUDE.md** for complete agent context and instructions.\n\nThis file exists for compatibility with tools that look for AGENTS.md.\n\n> **Recovery**: Run `gt prime` after compaction, clear, or new session\n\nFull context is injected by `gt prime` at session start.\n\n<!-- beads-agent-instructions-v2 -->\n\n---\n\n## Beads Workflow Integration\n\nThis project uses [beads](https://github.com/steveyegge/beads) for issue tracking. Issues live in `.beads/` and are tracked in git.\n\nTwo CLIs: **bd** (issue CRUD) and **bv** (graph-aware triage, read-only).\n\n### bd: Issue Management\n\n```bash\nbd ready              # Unblocked issues ready to work\nbd list --status=open # All open issues\nbd show <id>          # Full details with dependencies\nbd create --title=\"...\" --type=task --priority=2\nbd update <id> --status=in_progress\nbd close <id>         # Mark complete\nbd close <id1> <id2>  # Close multiple\nbd dep add <a> <b>    # a depends on b\nbd sync               # Sync with git\n```\n\n### bv: Graph Analysis (read-only)\n\n**NEVER run bare `bv`** — it launches interactive TUI. Always use `--robot-*` flags:\n\n```bash\nbv --robot-triage     # Ranked picks, quick wins, blockers, health\nbv --robot-next       # Single top pick + claim command\nbv --robot-plan       # Parallel execution tracks\nbv --robot-alerts     # Stale issues, cascades, mismatches\nbv --robot-insights   # Full graph metrics: PageRank, betweenness, cycles\n```\n\n### Workflow\n\n1. **Start**: `bd ready` (or `bv --robot-triage` for graph analysis)\n2. **Claim**: `bd update <id> --status=in_progress`\n3. **Work**: Implement the task\n4. **Complete**: `bd close <id>`\n5. **Sync**: `bd sync` at session end\n\n### Session Close Protocol\n\n```bash\ngit status            # Check what changed\ngit add <files>       # Stage code changes\nbd sync               # Commit beads changes\ngit commit -m \"...\"   # Commit code\nbd sync               # Commit any new beads changes\ngit push              # Push to remote\n```\n\n### Key Concepts\n\n- **Priority**: P0=critical, P1=high, P2=medium, P3=low, P4=backlog (numbers only)\n- **Types**: task, bug, feature, epic, question, docs\n- **Dependencies**: `bd ready` shows only unblocked work\n\n<!-- end-beads-agent-instructions -->\n\n<!-- gastown-agent-instructions-v1 -->\n\n---\n\n## Gas Town Multi-Agent Communication\n\nThis workspace is part of a **Gas Town** multi-agent environment. You communicate\nwith other agents using `gt` commands — never by printing text or using raw tmux.\n\n### Nudging Agents (Immediate Delivery)\n\n`gt nudge` sends a message directly to another agent's active session:\n\n```bash\ngt nudge mayor \"Status update: PR review complete\"\ngt nudge laneassist/crew/dom \"Check your mail — PR ready for review\"\ngt nudge witness \"Polecat health check needed\"\ngt nudge refinery \"Merge queue has items\"\n```\n\n**Target formats:**\n- Role shortcuts: `mayor`, `deacon`, `witness`, `refinery`\n- Full path: `<rig>/crew/<name>`, `<rig>/polecats/<name>`\n\n**Important:** `gt nudge` is the ONLY way to send text to another agent's session.\nNever print \"Hey @name\" — the other agent cannot see your terminal output.\n\n### Sending Mail (Persistent Messages)\n\n`gt mail` sends messages that persist across session restarts:\n\n```bash\n# Reading\ngt mail inbox                    # List messages\ngt mail read <id>                # Read a specific message\n\n# Sending (use --stdin for multi-line content)\ngt mail send mayor/ -s \"Subject\" -m \"Short message\"\ngt mail send laneassist/crew/dom -s \"PR Review\" --stdin <<'BODY'\nMulti-line message content here.\nDetails about the PR and what to look for.\nBODY\ngt mail send --human -s \"Subject\" -m \"Message to overseer\"\n```\n\n### When to Use Which\n\n| Want to... | Command | Why |\n|------------|---------|-----|\n| Wake a sleeping agent | `gt nudge <target> \"msg\"` | Immediate delivery |\n| Send detailed task/info | `gt mail send <target> -s \"...\" --stdin` | Persists across restarts |\n| Both: send + wake | `gt mail send` then `gt nudge` | Mail carries payload, nudge wakes |\n\n### Context Recovery\n\nAfter compaction or new session, run `gt prime` to reload your full role context,\nidentity, and any pending work.\n\n```bash\ngt prime              # Full context reload\ngt hook               # Check for assigned work\ngt mail inbox         # Check for messages\n```\n\n<!-- end-gastown-agent-instructions -->\n\n<!-- BEGIN BEADS INTEGRATION v:1 profile:minimal hash:ca08a54f -->\n## Beads Issue Tracker\n\nThis project uses **bd (beads)** for issue tracking. Run `gt prime` to see full workflow context and commands.\n\n### Quick Reference\n\n```bash\nbd ready              # Find available work\nbd show <id>          # View issue details\nbd update <id> --claim  # Claim work\nbd close <id>         # Complete work\n```\n\n### Rules\n\n- Use `bd` for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists\n- Run `gt prime` for detailed command reference and session close protocol\n- Use `bd remember` for persistent knowledge — do NOT use MEMORY.md files\n\n## Session Completion\n\n**When ending a work session**, you MUST complete ALL steps below. Work is NOT complete until `git push` succeeds.\n\n**MANDATORY WORKFLOW:**\n\n1. **File issues for remaining work** - Create issues for anything that needs follow-up\n2. **Run quality gates** (if code changed) - Tests, linters, builds\n3. **Update issue status** - Close finished work, update in-progress items\n4. **PUSH TO REMOTE** - This is MANDATORY:\n   ```bash\n   git pull --rebase\n   bd dolt push\n   git push\n   git status  # MUST show \"up to date with origin\"\n   ```\n5. **Clean up** - Clear stashes, prune remote branches\n6. **Verify** - All changes committed AND pushed\n7. **Hand off** - Provide context for next session\n\n**CRITICAL RULES:**\n- Work is NOT complete until `git push` succeeds\n- NEVER stop before pushing - that leaves work stranded locally\n- NEVER say \"ready to push when you are\" - YOU must push\n- If push fails, resolve and retry until it succeeds\n<!-- END BEADS INTEGRATION -->\n","category":"root","tokens":1492}]}