---

name: clue-workspace description: Expert guidance for clue workspace coordination. Use when working in a directory with .clue/, when multiple Claude sessions need coordination, or when managing repositories in a shared workspace.

Clue Workspace Coordination

You are working in a clue workspace - a coordinated environment for multi-agent development.

Core Philosophy

1. Workspace isolation - All work stays within this directory tree
2. Shared awareness - Goals, notes, and repo status are visible to all sessions
3. Conflict prevention - Each session uses isolated branches/worktrees

Available Tools

Repository Structure

Clue workspaces use bare clones and worktrees for safe parallel work:

Copyworkspace/
  .clue/
  repos/
    backend.git           # bare clone (shared, read-only)
    frontend.git          # bare clone
  backend-feature-auth/   # worktree at root (session A)
  frontend-fix-bug/       # worktree at root (session B)

Key rules:

• repos/ contains only bare clones (.git suffix)
• Worktrees live at workspace root: <repo>-<branch>/
• Never modify bare clones directly

Instructions for Claude

When working in a clue workspace:

1. Before modifying code:

   • Run clue status to check for other active sessions
   • Create a worktree to isolate your changes:

     Copygit -C repos/<name>.git worktree add -b <branch> ../../<name>-<branch>
     

2. When repos seem stale or missing:

   • Run clue repo scan to refresh repo tracking
   • Run clue repo list to see tracked repos

3. To coordinate with other sessions:

   • Add notes: clue note add "working on X"
   • Check pinned notes for context from others

4. Always use worktrees for code changes to avoid conflicts with other sessions

Quick Reference

Copyclue status          # What's happening in this workspace?
clue status full     # Full workspace details
clue repo scan       # Refresh repo tracking
clue repo list       # What repos are tracked?
clue repo add <url>  # Clone and track a repository
clue help            # All available commands