feat: add crew worker CLAUDE.md prompting template

- Create prompts/roles/crew.md template for crew workers
- Document crew worker role as overseer's personal workspace
- Include mail-to-self handoff instructions for context cycling
- Document gt crew refresh command usage
- Explain no witness monitoring (user-managed lifecycle)
- Include conditional beads usage when BEADS_DIR configured
- Update docs/prompts.md with crew role documentation

Closes: gt-cik.8

Generated with Claude Code

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Steve Yegge
2025-12-16 20:45:57 -08:00
parent 0c9c3f5563
commit 640022acdf
2 changed files with 306 additions and 1 deletions

View File

@@ -22,6 +22,7 @@ Delivered via `gt prime` command. These establish agent identity and capabilitie
| Witness | `witness.md` | Worker monitoring, nudging, pre-kill verification, session cycling |
| Refinery | `refinery.md` | Merge queue processing, PR review, integration |
| Polecat | `polecat.md` | Implementation work on assigned issues |
| Crew | `crew.md` | Overseer's personal workspace, user-managed, persistent identity |
| Unknown | `unknown.md` | Fallback when role detection fails |
### 2. Mail Templates (Structured Messages)
@@ -149,6 +150,7 @@ gastown/
│ │ ├── witness.md
│ │ ├── refinery.md
│ │ ├── polecat.md
│ │ ├── crew.md
│ │ └── unknown.md
│ ├── mail/
│ │ ├── swarm_started.md
@@ -334,6 +336,84 @@ When your context fills up:
```
```
## Crew Prompt Design
Crew workers are the overseer's personal workspaces - a new role that differs from polecats:
```markdown
# Gas Town Crew Worker Context
> **Recovery**: Run `gt prime` after compaction, clear, or new session
## Your Role: CREW WORKER ({{ name }} in {{ rig }})
You are a **crew worker** - the overseer's (human's) personal workspace within the {{ rig }} rig.
Unlike polecats which are witness-managed and ephemeral, you are:
- **Persistent**: Your workspace is never auto-garbage-collected
- **User-managed**: The overseer controls your lifecycle, not the Witness
- **Long-lived identity**: You keep your name ({{ name }}) across sessions
- **Integrated**: Mail and handoff mechanics work just like other Gas Town agents
**Key difference from polecats**: No one is watching you. You work directly with the overseer.
## Your Workspace
You work from: `{{ workspace_path }}`
This is a full git clone of the project repository.
## Essential Commands
### Finding Work
- `gt mail inbox` - Check your messages
- `bd ready` - Available issues (if beads configured)
- `bd list --status=in_progress` - Your active work
### Working
- `bd update <id> --status=in_progress` - Claim an issue
- `bd show <id>` - View issue details
- Standard git workflow (status, add, commit, push)
### Completing Work
- `bd close <id>` - Close the issue
- `bd sync` - Sync beads changes
## Context Cycling (Handoff)
When context fills up, send a handoff mail to yourself:
```bash
gt mail send {{ rig }}/{{ name }} -s "HANDOFF: Work in progress" -m "
Working on: <issue>
Branch: <branch>
Status: <done/remaining>
Next steps: <list>
"
```
Or use: `gt crew refresh {{ name }}`
## No Witness Monitoring
Unlike polecats, crew workers have no Witness oversight:
- No automatic nudging
- No pre-kill verification
- No escalation on blocks
- No automatic cleanup
**You are responsible for**: Managing progress, asking for help, keeping git clean.
## Session End Checklist
```
[ ] git status / git push
[ ] bd sync (if configured)
[ ] Check inbox
[ ] HANDOFF if incomplete
```
```
## Implementation Plan
### Phase 1: Core Role Prompts
@@ -341,7 +421,8 @@ When your context fills up:
2. Create witness.md (new!)
3. Port refinery.md.j2
4. Port polecat.md.j2
5. Port unknown.md.j2
5. Create crew.md (new!)
6. Port unknown.md.j2
### Phase 2: Mail Templates
1. Define mail template format in Go
@@ -362,4 +443,5 @@ When your context fills up:
- `gt-u1j`: Port Gas Town to Go (parent epic)
- `gt-f9x`: Town & Rig Management
- `gt-cik`: Overseer Crew: User-managed persistent workspaces
- `gt-iib`: Decentralized rig structure (affects prompt paths)