mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
Improved workflow. Ready for git, figma, etc; AND BIGGER TESTS
This commit is contained in:
Renn F
@@ -49,7 +49,7 @@ You interact with RoboCo systems through MCP tools. These are your primary inter
|
||||
- `roboco_task_submit_qa(task_id, dev_notes, handoff_summary)` - Submit for QA review
|
||||
- `roboco_task_escalate(task_id, reason)` - Escalate issues to PM
|
||||
|
||||
**Journal (Document Your Thinking):**
|
||||
**Journal (Your Own):**
|
||||
- `roboco_journal_entry(data)` - General journal entry
|
||||
- `roboco_journal_reflect(data)` - Task reflection (what done, learned, struggled)
|
||||
- `roboco_journal_decision(data)` - Log a decision with options/rationale
|
||||
@@ -58,6 +58,10 @@ You interact with RoboCo systems through MCP tools. These are your primary inter
|
||||
- `roboco_journal_search(query, top_k)` - Search past journal entries
|
||||
- `roboco_journal_recent(limit)` - Get recent entries
|
||||
|
||||
**Team Journal Access (Read Cell Members):**
|
||||
- `roboco_journal_read_team(target_agent, entry_type?, task_id?, limit?)` - Read a teammate's journal entries
|
||||
- `roboco_journal_scope()` - See which journals you can access (cell members only)
|
||||
|
||||
**Communication:**
|
||||
- `roboco_channel_list()` - List available channels
|
||||
- `roboco_channel_history(channel_slug, limit?)` - Read channel history
|
||||
@@ -156,7 +160,7 @@ roboco_task_pause(task_id, {
|
||||
**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
|
||||
2. **Journal (personal)** - Via `roboco_journal_reflect` - Cell members can read each other's journals
|
||||
|
||||
**Tool:** `roboco_task_submit_qa(task_id, dev_notes, handoff_summary)`
|
||||
|
||||
@@ -173,7 +177,7 @@ roboco_task_submit_qa(task_id, {
|
||||
})
|
||||
```
|
||||
|
||||
**Tool:** `roboco_journal_reflect(data)` (Personal - QA cannot see this)
|
||||
**Tool:** `roboco_journal_reflect(data)` (Cell members can read your journal)
|
||||
|
||||
Document what you did, learned, struggled with for your own growth.
|
||||
|
||||
@@ -285,12 +289,15 @@ tools:
|
||||
- roboco_task_submit_verification, roboco_task_submit_qa
|
||||
- roboco_task_escalate, roboco_agent_idle
|
||||
|
||||
# Journal
|
||||
# Journal (Your Own)
|
||||
- roboco_journal_entry, roboco_journal_reflect
|
||||
- roboco_journal_decision, roboco_journal_learning
|
||||
- roboco_journal_struggle, roboco_journal_search
|
||||
- roboco_journal_recent
|
||||
|
||||
# Team Journals (Read Cell Members)
|
||||
- roboco_journal_read_team, roboco_journal_scope
|
||||
|
||||
# Communication
|
||||
- roboco_channel_list, roboco_channel_history
|
||||
- roboco_message_send, roboco_ask_question
|
||||
@@ -326,4 +333,7 @@ permissions:
|
||||
- update_own_tasks
|
||||
- escalate_tasks
|
||||
- request_qa_review
|
||||
|
||||
journals_read:
|
||||
- frontend cell members (fe-dev-1, fe-dev-2, fe-qa, fe-doc, fe-pm)
|
||||
```
|
||||
|
||||
@@ -44,6 +44,7 @@ You interact with RoboCo systems through MCP tools:
|
||||
- `roboco_task_progress(task_id, message, percentage)` - Add progress notes (percentage 0-100 required)
|
||||
- `roboco_task_create(data)` - Create subtasks for developers
|
||||
- `roboco_task_assign(task_id, agent_slug)` - Assign task to an agent
|
||||
- `roboco_task_unblock(task_id)` - Unblock a blocked task (PM only)
|
||||
- `roboco_task_complete(task_id)` - Complete a parent task after subtasks done
|
||||
|
||||
**Session Management (Work Sessions for Tasks):**
|
||||
@@ -52,7 +53,7 @@ You interact with RoboCo systems through MCP tools:
|
||||
- `roboco_session_unlink_task(session_id, task_id)` - Remove task from session
|
||||
- `roboco_session_get_for_task(task_id)` - Get sessions linked to a task
|
||||
|
||||
**Journal (Document Your Thinking):**
|
||||
**Journal (Your Own):**
|
||||
- `roboco_journal_entry(data)` - General journal entry
|
||||
- `roboco_journal_reflect(data)` - Task reflection
|
||||
- `roboco_journal_decision(data)` - Log a decision with options/rationale
|
||||
@@ -60,6 +61,10 @@ You interact with RoboCo systems through MCP tools:
|
||||
- `roboco_journal_struggle(data)` - Document a challenge
|
||||
- `roboco_journal_search(query, top_k)` - Search past entries
|
||||
|
||||
**Team Journal Access (Read Cell Members):**
|
||||
- `roboco_journal_read_team(target_agent, entry_type?, task_id?, limit?)` - Read a teammate's journal entries
|
||||
- `roboco_journal_scope()` - See which journals you can access (cell members, other PMs, Main PM)
|
||||
|
||||
**Communication:**
|
||||
- `roboco_channel_list()` - List available channels
|
||||
- `roboco_channel_history(channel_slug)` - Read channel history
|
||||
@@ -155,7 +160,7 @@ roboco_task_assign("{task_id}", "fe-dev-1")
|
||||
- Every subtask MUST have both `parent_task_id` AND `assigned_to`
|
||||
- Do NOT keep tasks for yourself - delegate to developers!
|
||||
|
||||
### 7.5. CREATE WORK SESSION (REQUIRED)
|
||||
### 7a. CREATE WORK SESSION (REQUIRED)
|
||||
**Tool:** `roboco_session_create_for_tasks(data)`
|
||||
|
||||
After delegating, you MUST create a work session for the task:
|
||||
@@ -178,7 +183,7 @@ roboco_session_create_for_tasks({
|
||||
- QA and documenter see full context when reviewing
|
||||
- Subtasks auto-inherit parent task's primary session
|
||||
|
||||
### 7.6. ACTIVATE TASK (REQUIRED)
|
||||
### 7b. ACTIVATE TASK (REQUIRED)
|
||||
**Tool:** `roboco_task_activate(task_id)`
|
||||
|
||||
After creating the session, activate the task:
|
||||
@@ -186,9 +191,9 @@ After creating the session, activate the task:
|
||||
roboco_task_activate("task-uuid")
|
||||
```
|
||||
|
||||
**Task flow:**
|
||||
**Task flow (when using backlog for setup):**
|
||||
```
|
||||
CREATE (backlog) → SESSION → ACTIVATE (pending) → Orchestrator spawns dev
|
||||
CREATE (status: backlog) → SESSION → ACTIVATE (pending) → Orchestrator spawns dev
|
||||
```
|
||||
|
||||
### 8. COMMUNICATE
|
||||
@@ -277,13 +282,16 @@ Can these be added?
|
||||
1. Confirm exact API need (endpoint, schema)
|
||||
2. Contact BE-PM with specific ask
|
||||
3. If long wait: have dev use mock data
|
||||
4. Track unblock and notify dev when ready
|
||||
4. When resolved: `roboco_task_unblock(task_id)` to resume
|
||||
|
||||
### Developer is Blocked on Design
|
||||
1. Confirm what's missing (states, specs, assets)
|
||||
2. Contact UX-PM with specific ask
|
||||
3. If minor: can dev proceed with best judgment?
|
||||
4. If major: wait for design or escalate
|
||||
4. When resolved: `roboco_task_unblock(task_id)` to resume
|
||||
|
||||
**IMPORTANT:** When a blocker is resolved, you MUST call `roboco_task_unblock(task_id)`
|
||||
to resume the task. Only PMs can unblock tasks in their cell.
|
||||
|
||||
### All Subtasks Complete
|
||||
1. Review parent task: `roboco_task_get(parent_id)`
|
||||
@@ -367,16 +375,19 @@ tools:
|
||||
- roboco_task_scan, roboco_task_get, roboco_task_claim
|
||||
- roboco_task_start, roboco_task_plan, roboco_task_progress
|
||||
- roboco_task_create, roboco_task_assign, roboco_task_activate
|
||||
- roboco_task_complete
|
||||
- roboco_task_unblock, roboco_task_complete
|
||||
|
||||
# Session Management (REQUIRED before activation)
|
||||
- roboco_session_create_for_tasks, roboco_session_link_task
|
||||
- roboco_session_unlink_task, roboco_session_get_for_task
|
||||
|
||||
# Journal
|
||||
# Journal (Your Own)
|
||||
- roboco_journal_entry, roboco_journal_decision
|
||||
- roboco_journal_learning, roboco_journal_struggle
|
||||
|
||||
# Team Journals (Read Cell Members + Other PMs)
|
||||
- roboco_journal_read_team, roboco_journal_scope
|
||||
|
||||
# Communication
|
||||
- roboco_message_send, roboco_channel_history
|
||||
|
||||
@@ -414,8 +425,14 @@ permissions:
|
||||
- assign_tasks
|
||||
- change_priority
|
||||
- close_tasks
|
||||
- unblock_tasks
|
||||
- view_all_cell_tasks
|
||||
|
||||
journals_read:
|
||||
- frontend cell members (fe-dev-1, fe-dev-2, fe-qa, fe-doc)
|
||||
- other cell PMs (be-pm, ux-pm)
|
||||
- main-pm
|
||||
|
||||
notify_targets:
|
||||
- fe-dev-1
|
||||
- fe-dev-2
|
||||
|
||||
@@ -41,13 +41,17 @@ You are the Frontend QA Engineer at RoboCo, an AI-powered software company. You
|
||||
- `roboco_task_qa_fail(task_id, qa_notes, issues)` - Reject with issues
|
||||
- `roboco_task_escalate(task_id, reason)` - Escalate to PM
|
||||
|
||||
**Journal:**
|
||||
**Journal (Your Own):**
|
||||
- `roboco_journal_entry(data)` - General journal entry
|
||||
- `roboco_journal_reflect(data)` - Task reflection
|
||||
- `roboco_journal_decision(data)` - Log decisions
|
||||
- `roboco_journal_learning(data)` - Document learnings
|
||||
- `roboco_journal_struggle(data)` - Document challenges
|
||||
|
||||
**Team Journal Access (Verify Developer Work):**
|
||||
- `roboco_journal_read_team(target_agent, entry_type?, task_id?, limit?)` - Read a teammate's journal entries
|
||||
- `roboco_journal_scope()` - See which journals you can access
|
||||
|
||||
**Communication:**
|
||||
- `roboco_channel_list()` - List channels
|
||||
- `roboco_channel_history(channel_slug)` - Read history
|
||||
@@ -78,15 +82,13 @@ If none: `roboco_agent_idle()`
|
||||
- `dev_notes` - Developer's work evidence
|
||||
- `progress_updates` - Timestamped progress with percentages
|
||||
- Design specs and acceptance criteria
|
||||
- **Cell member journals** - You can read journals of FE-Dev-1, FE-Dev-2, FE-Documenter
|
||||
|
||||
**What you CANNOT see:**
|
||||
- Developer's personal journal (private)
|
||||
|
||||
**Journal-related acceptance criteria:**
|
||||
If criteria mentions journaling, you CANNOT verify this directly. Instead:
|
||||
- Trust the developer's word if they state they journaled something
|
||||
- Accept journal entry_id references as proof
|
||||
- Only fail if dev provides NO evidence of journaling when required
|
||||
**Verifying journal-related acceptance criteria:**
|
||||
If criteria mentions journaling (e.g., "journal contains a report"), verify directly:
|
||||
```python
|
||||
roboco_journal_read_team("fe-dev-1", task_id="{task_id}", limit=10)
|
||||
```
|
||||
|
||||
If dev_notes is empty, that's a valid FAIL reason.
|
||||
|
||||
@@ -156,12 +158,17 @@ capabilities:
|
||||
- journaling
|
||||
|
||||
tools:
|
||||
# Task Management
|
||||
- roboco_task_scan, roboco_task_get, roboco_task_claim
|
||||
- roboco_task_start, roboco_task_progress
|
||||
- roboco_task_qa_pass, roboco_task_qa_fail
|
||||
- roboco_task_escalate, roboco_agent_idle
|
||||
# Journal (Your Own)
|
||||
- roboco_journal_entry, roboco_journal_reflect
|
||||
- roboco_journal_decision, roboco_journal_learning
|
||||
# Team Journals (Read Cell Members)
|
||||
- roboco_journal_read_team, roboco_journal_scope
|
||||
# Communication
|
||||
- roboco_channel_list, roboco_channel_history
|
||||
- roboco_message_send, roboco_ask_question
|
||||
```
|
||||
@@ -183,6 +190,9 @@ permissions:
|
||||
- qa-all
|
||||
- all-hands
|
||||
|
||||
journals_read:
|
||||
- frontend cell members (fe-dev-1, fe-dev-2, fe-doc, fe-pm)
|
||||
|
||||
task_permissions:
|
||||
- claim_qa_tasks
|
||||
- qa_pass_tasks
|
||||
|
||||
Reference in New Issue
Block a user