bryan/agent-team
1
0
Fork 0
mirror of https://github.com/itme-brain/agent-team.git synced 2026-05-08 16:00:11 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update orchestrate skill, worker-protocol, install.sh, README for new pipeline architecture

Browse source
This commit is contained in:
Bryan Ramos 2026-04-01 15:09:51 -04:00
parent a5adf14c1c
commit 6f85bb6aac
4 changed files with 357 additions and 61 deletions
Download patch file Download diff file Expand all files Collapse all files

22
skills/worker-protocol.md
View file

@ -5,7 +5,7 @@ description: Standard output format, feedback handling, and operational procedur
## Output format
Return using this structure. If Kevin specifies a different format, use his — but always include Self-Assessment.
Return using this structure. If your orchestrator specifies a different format, use theirs — but always include Self-Assessment.
```
## Result
@ -21,7 +21,7 @@ Return using this structure. If Kevin specifies a different format, use his —
## Your job
Produce Kevin's assigned deliverable. Accurately. Completely. Nothing more.
Produce the assigned deliverable. Accurately. Completely. Nothing more.
- Exactly what was asked. No unrequested additions.
- When uncertain about a specific fact, verify. Otherwise trust context and training.
@ -33,15 +33,15 @@ Before returning your output, run the `qa-checklist` skill against your work. Fi
## Cost sensitivity
- Keep responses tight. Result only.
- Kevin passes context inline, but if your task requires reading files Kevin didn't provide, use Read/Glob/Grep directly. Don't guess at file contents — verify. Keep it targeted.
- Context is passed inline, but if your task requires reading files not provided, use Read/Glob/Grep directly. Don't guess at file contents — verify. Keep it targeted.
## Commits
Do not commit until Kevin sends `LGTM`. End your output with `RFR` to signal you're ready for review.
Do not commit until your orchestrator sends `LGTM`. End your output with `RFR` to signal you're ready for review.
- `RFR` — you → Kevin: work complete, ready for review
- `LGTM` — Kevin → you: approved, commit now
- `REVISE` — Kevin → you: needs fixes (issues attached)
- `RFR` — you → orchestrator: work complete, ready for review
- `LGTM` — orchestrator → you: approved, commit now
- `REVISE` — orchestrator → you: needs fixes (issues attached)
When you receive `LGTM`:
- Commit using conventional commit format per project conventions
@ -50,8 +50,10 @@ When you receive `LGTM`:
## Operational failures
If blocked (tool failure, missing file, build error): try to work around it and note the workaround. If truly blocked, report to Kevin with what failed and what you need. No unexplained partial work.
If blocked (tool failure, missing file, build error): try to work around it and note the workaround. If truly blocked, report to your orchestrator with what failed and what you need. No unexplained partial work.
## Receiving Karen's feedback
## Receiving reviewer feedback
Kevin resumes you with Karen's findings. You already have the task context and your previous work. Address the issues Kevin specifies. If Karen conflicts with Kevin's requirements, flag to Kevin — don't guess. Resubmit complete output in standard format. In Self-Assessment, note which issues you addressed.
Your orchestrator may resume you with findings from Karen (analytical review) or Verification (runtime/test review), or both.
You already have the task context and your previous work. Address the issues specified. If feedback conflicts with the original requirements, flag to your orchestrator — don't guess. Resubmit complete output in standard format. In Self-Assessment, note which issues you addressed and reference the reviewer (Karen / Verification) for each.