Added git workflow + fixing some issues

agents/prompts/roles/cell_pm.md

@@ -79,7 +79,7 @@ roboco_task_create(
     parent_task_id=my_task["id"],  # REQUIRED - links to your task
     assigned_to="be-dev-1",  # Developer - task will flow to QA/Doc automatically
     task_type="code",
-    requires_git=True,
+    project_slug="roboco",  # REQUIRED - all tasks need a project
     team="backend",
     ...
 )
@@ -97,8 +97,8 @@ roboco_task_create(
 
 **Task Types for Subtasks:**
 - Use `task_type: "code"` for developer work that modifies files
-- Use `requires_git: true` for code changes
-- Use `task_type: "research"` for investigation without code changes
+- Use `task_type: "research"` for investigation (still commits research notes)
+- All tasks follow git workflow automatically
 
 ### 5. ACTIVATE
 `roboco_task_activate()` moves backlog → pending. Now visible to devs.
@@ -141,7 +141,7 @@ roboco_task_unblock(
 - ✅ Call `roboco_task_unblock()` with clear resolution notes
 - ✅ The system will notify and respawn the developer automatically
 
-### 9. REVIEW PR (Git Tasks)
+### 9. REVIEW PR
 When subtasks reach `awaiting_pm_review`:
 1. Review the PR: `roboco_git_diff(project_slug)` to see changes
 2. Check QA notes and documentation
@@ -158,6 +158,7 @@ When ALL subtasks done: reflect + complete your task.
 
 **Task Management:**
 - `roboco_task_scan`, `roboco_task_get`, `roboco_task_claim`
+- `roboco_task_unclaim` (release claimed task if wrong fit)
 - `roboco_task_create`, `roboco_task_assign`, `roboco_task_activate`
 - `roboco_task_plan`, `roboco_task_start`, `roboco_task_progress`
 - `roboco_task_complete`, `roboco_task_cancel`

agents/prompts/roles/developer.md

@@ -48,11 +48,9 @@ Use `roboco_task_scan(team)` for pending tasks assigned to you or unassigned.
 ### 3. CLAIM
 Use `roboco_task_claim()`. Status: pending → claimed.
 
-### 4. CHECKOUT (Git Tasks)
-**For tasks with `requires_git=True`:**
-- Branch auto-created when you claimed the task
-- **Auto-checkout happens on `roboco_task_start()`** - no manual checkout needed
-- System blocks if you have uncommitted changes
+### 4. CHECKOUT
+Branch is auto-created when you claim the task. Auto-checkout happens on `roboco_task_start()`.
+System blocks if you have uncommitted changes.
 
 ### 5. RESEARCH
 Search KB and journals before planning: `roboco_kb_search()`, `roboco_rag_query()`, `roboco_journal_search()`.
@@ -126,11 +124,12 @@ If PMs request changes:
 
 **Task Management:**
 - `roboco_task_scan`, `roboco_task_get`, `roboco_task_claim`
+- `roboco_task_unclaim` (release claimed task if wrong fit)
 - `roboco_task_plan`, `roboco_task_start`, `roboco_task_progress`
 - `roboco_task_block`, `roboco_task_unblock`, `roboco_task_pause`, `roboco_task_escalate`
 - `roboco_task_submit_verification`, `roboco_task_submit_qa`
 - `roboco_task_submit_pm_review` (non-dev tasks, skips QA)
-- `roboco_task_substitute` (graceful exit)
+- `roboco_task_substitute` (graceful exit from in_progress)
 
 **Git (Read-Only):**
 - `roboco_git_status(project_slug)` - Current branch, staged/unstaged changes

agents/prompts/roles/documenter.md

@@ -28,8 +28,7 @@ Use `roboco_task_claim()`. Status: awaiting_documentation → claimed.
 ### 3. START
 Use `roboco_task_start()` then `roboco_message_send()` to announce.
 
-### 4. CHECKOUT (Git Tasks)
-**For tasks with `requires_git=True`:**
+### 4. CHECKOUT
 1. Check branch status: `roboco_git_status(project_slug)`
 2. The task's `branch_name` tells you which branch has the code
 3. Review dev's commits: `roboco_git_log(project_slug)`
@@ -61,8 +60,8 @@ roboco_docs_write({
 
 Update progress: `roboco_task_progress()`
 
-### 7. COMMIT (Git Tasks)
-**For tasks with `requires_git=True`:**
+### 7. COMMIT
+**Commit your documentation to the branch:**
 1. Commit your documentation: `roboco_git_commit(project_slug, message, task_id)`
    - Example message: `docs: add API documentation for user endpoints`
 2. Push your changes: `roboco_git_push(project_slug, task_id)`
@@ -84,6 +83,7 @@ Use `roboco_task_docs_complete()`. This sets `docs_complete=True`.
 
 **Task Management:**
 - `roboco_task_scan`, `roboco_task_get`, `roboco_task_claim`
+- `roboco_task_unclaim` (release claimed task if wrong fit)
 - `roboco_task_start`, `roboco_task_progress`
 - `roboco_task_docs_complete`
 - `roboco_task_escalate`, `roboco_task_substitute`

agents/prompts/roles/main_pm.md

@@ -77,7 +77,7 @@ roboco_task_create(
 - Completion tracking breaks
 - Your task can't complete
 
-- Set `project_id` for git tasks (branches are auto-created on claim)
+- Set `project_id` (required - branches are auto-created on claim)
 
 ### 6. ACTIVATE + NOTIFY
 `roboco_task_activate()` each task, then `roboco_notify_send()` to each Cell PM. REQUIRED.
@@ -96,7 +96,7 @@ When respawned: scan, read Cell PM journals, update progress, handle escalated b
 
 **DO NOT just send a message and hope they figure it out. CALL UNBLOCK.**
 
-### 9. REVIEW PR (Git Tasks)
+### 9. REVIEW PR
 When cell tasks reach `awaiting_pm_review` and all subtasks are merged:
 1. Review the parent PR (all subtask work combined)
 2. Coordinate with Cell PM - **BOTH must approve**

agents/prompts/roles/qa.md

@@ -21,8 +21,7 @@ Use `roboco_task_claim()`. QA can ONLY claim from `awaiting_qa` status.
 ### 3. START
 Use `roboco_task_start()` then `roboco_message_send()` to announce.
 
-### 4. CHECKOUT (Git Tasks)
-**For tasks with `requires_git=True`:**
+### 4. CHECKOUT
 1. Check branch status: `roboco_git_status(project_slug)`
 2. The task's `branch_name` tells you which branch to review
 3. Review the branch diff vs main: `roboco_git_diff(project_slug)`
@@ -52,6 +51,7 @@ Use `roboco_journal_reflect()` before decision. REQUIRED.
 
 **Task Management:**
 - `roboco_task_scan`, `roboco_task_get`, `roboco_task_claim`
+- `roboco_task_unclaim` (release claimed task if wrong fit)
 - `roboco_task_start`, `roboco_task_progress`
 - `roboco_task_qa_pass`, `roboco_task_qa_fail`
 - `roboco_task_escalate`, `roboco_task_substitute`