docs: add workflow notes for agent task document creation

Document the correct workflow to ensure agent task documents are
available in agent workspaces. Task docs must be committed to main
before creating the agent workspace.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: luke

docs/agents/README.md

@@ -348,4 +348,41 @@ Here's a template that works well:
 4. **Concrete > Abstract**: Specific file paths, exact commands
 5. **Testable > Theoretical**: Include ways to verify success
 
-Remember: A well-written task document should enable an agent to start coding within minutes, not spend hours figuring out what to do.
+Remember: A well-written task document should enable an agent to start coding within minutes, not spend hours figuring out what to do.
+
+## Important Workflow Notes
+
+### Creating Agent Task Documents
+
+When creating task documents for agents, follow this workflow to ensure they're available in the agent's workspace:
+
+1. **Create the task document on main branch**
+2. **Commit and push to main BEFORE opening the agent**
+3. **Then create the agent workspace**
+
+**❌ Common Mistake**: Creating the task document after the agent workspace exists means the agent won't have access to it.
+
+**✅ Correct Workflow**:
+```bash
+# 1. On main branch, create the task document
+cat > docs/agents/AGENT_N_TASK.md << 'EOF'
+# Task content...
+EOF
+
+# 2. Commit and push
+git add docs/agents/AGENT_N_TASK.md
+git commit -m "docs: add Agent N task"
+git push origin main
+
+# 3. NOW create the agent
+./agent start N
+```
+
+**If you've already created the agent**, the agent needs to pull from main:
+```bash
+# Agent will need to run in their workspace:
+git fetch origin main
+git merge origin main
+```
+
+This ensures agents always have access to their task documentation and any other resources committed to main.