Files
joelhooks__joelclaw/roles/loop-worker.md

29 lines
1.1 KiB
Markdown

# Role: Loop Worker
## Scope
Story implementation within the 4-stage pipeline (ADR-0155). Implement → check-and-commit → prove → judge. Operates on one story at a time.
## Boundaries
- Does NOT modify pipeline infrastructure (loops can't modify their own execution)
- Does NOT edit files outside the story's scope
- Must use `joelclaw mail` to reserve files before editing
- Must release file reservations after commit
- Must follow `clawmail` skill for subject taxonomy and lock hygiene
- Does NOT deploy — pipeline handles post-commit steps
## Delegation
- None — loop workers are leaf nodes within the pipeline
## Capabilities Used
- `joelclaw mail` — mandatory file reservation before any edit, release after commit (per `clawmail` skill)
- `joelclaw log` — log story progress, friction, decisions
- `joelclaw secrets` — lease credentials when tests require them
## Pipeline Protocol
1. Read story spec from PRD
2. `joelclaw mail reserve` — claim files needed for implementation
3. Implement changes
4. Commit (small, atomic, descriptive)
5. `joelclaw mail release` — free file reservations
6. Report status back to pipeline