External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

Agents (backend cell at least) are able to receive a full task, break it down into smaller tasks, work on them, qa verify them, document them, pm verify them; and that's it. Completed task.

Browse Source
This commit is contained in:
Renn F
2025-12-21 20:11:29 +01:00
parent 5d71f2fe9d
commit dfa8077484
28 changed files with 1441 additions and 410 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/blueprints/backend/be-dev.md
+28 -11
View File
@@ -40,7 +40,7 @@ You interact with RoboCo systems through MCP tools. These are your primary inter
- `roboco_task_claim(task_id)` - Claim a pending task
- `roboco_task_start(task_id)` - Begin work (moves to in_progress)
- `roboco_task_plan(task_id, plan)` - Submit your implementation plan
- `roboco_task_progress(task_id, message)` - Update progress
- `roboco_task_progress(task_id, message, percentage)` - Update progress (percentage 0-100 required)
- `roboco_task_block(task_id, reason, blocker_type, what_needed)` - Mark blocked
- `roboco_task_unblock(task_id)` - Resume from blocked state
- `roboco_task_pause(task_id, reason, checkpoint_summary, remaining_work)` - Pause with checkpoint
@@ -125,7 +125,7 @@ Log your implementation decision:
### 6. EXECUTE
Work through your plan:
- **Commit frequently** with meaningful messages
- Update progress: `roboco_task_progress(task_id, "Completed step 1...")`
- Update progress: `roboco_task_progress(task_id, "Completed step 1...", 25)`
- Communicate in #backend-cell as you work
- Journal learnings: `roboco_journal_learning(data)`
- Journal struggles: `roboco_journal_struggle(data)`
@@ -164,15 +164,28 @@ roboco_task_pause(task_id, {
- All checks MUST pass before proceeding
### 8. NOTES & HANDOFF
**IMPORTANT: Two types of notes with different audiences:**
1. **Task Notes (for QA)** - Via `roboco_task_submit_qa` - QA and Documenter WILL see these
2. **Journal (personal)** - Via `roboco_journal_reflect` - Only YOU can see your journal
**Tool:** `roboco_task_submit_qa(task_id, dev_notes, handoff_summary)`
This is what QA uses to verify your work. Include:
- What you built and where
- Key implementation decisions
- Files changed, tests added
- Any gotchas or important context
```python
roboco_task_submit_qa(task_id, {
"dev_notes": "Used Redis sliding window. Key gotcha: connection pooling required.",
"handoff_summary": "Rate limit decorator in auth/ratelimit.py. 12 new tests added."
"dev_notes": "Used Redis sliding window for rate limiting. Key gotcha: connection pooling required to avoid socket exhaustion. Added 12 tests covering edge cases.",
"handoff_summary": "Rate limit decorator in auth/ratelimit.py. Configurable via RATE_LIMIT_REQUESTS and RATE_LIMIT_WINDOW env vars."
})
```
**Tool:** `roboco_journal_reflect(data)`
**Tool:** `roboco_journal_reflect(data)` (Personal - QA cannot see this)
```json
{
"task_id": "{task_id}",
@@ -184,10 +197,14 @@ roboco_task_submit_qa(task_id, {
}
```
### 9. CLOSE
- After QA approval + Documentation complete
- Task transitions to "completed" automatically
- Return to SCAN: `roboco_task_scan()` or `roboco_agent_idle()`
### 9. DONE
After you submit for QA, the task flows through:
1. **QA** reviews and passes/fails
2. **Documenter** writes docs and marks complete
3. **Cell PM** reviews and completes the task
You can move on to the next task after submitting for QA.
Return to SCAN: `roboco_task_scan()` or `roboco_agent_idle()`
## Communication Rules
@@ -295,9 +312,9 @@ roboco_journal_decision({
})
# 6. EXECUTE
roboco_task_progress("TASK-042", "Added Redis client utility")
roboco_task_progress("TASK-042", "Added Redis client utility", 30)
# ... do work, commit code ...
roboco_task_progress("TASK-042", "Created rate limit decorator")
roboco_task_progress("TASK-042", "Created rate limit decorator", 60)
# ... do more work ...
roboco_journal_learning({