Subject: [Clear, specific title]

BACKGROUND:
[Why is this being requested? What led to this need?]

CURRENT STATE:
[What's already done? What files/work exists?]

SPECIFIC ASK:
[Exactly what action is needed from the recipient?]

FILES:
- [Full path to file 1] - [purpose]
- [Full path to file 2] - [purpose]

SUCCESS CRITERIA:
[How will the recipient know they did it correctly?]

mcp__orchestrator__send_message(
    to_project="claude-family-manager",
    message_type="task_request",
    subject="Implement user authentication flow",
    body="""
BACKGROUND:
We're adding login functionality to the app. The UI is complete but needs
backend integration with the PostgreSQL database.

CURRENT STATE:
- LoginPage.xaml exists at src/Views/LoginPage.xaml
- LoginViewModel stub at src/ViewModels/LoginViewModel.cs
- User table exists in database with password_hash column
- API client infrastructure not yet implemented

SPECIFIC ASK:
Implement the login API call and wire up the ViewModel to handle user login.

FILES:
- src/ViewModels/LoginViewModel.cs - Wire up login command
- src/Services/AuthService.cs - Create new, implement login logic
- src/Models/LoginRequest.cs - Create new, login request DTO
- src/Models/LoginResponse.cs - Create new, login response DTO

SUCCESS CRITERIA:
- User can enter email/password and click Login button
- Success → navigates to DashboardPage with user context
- Failure → shows error message in UI (invalid credentials, network error, etc.)
- Passwords are never logged or stored in plaintext
    """,
    priority="normal"
)

mcp__orchestrator__send_message(
    to_project="claude-family-manager",
    message_type="task_request",
    subject="Fix the login",
    body="Please implement the authentication we discussed.",
    priority="normal"
)

/check-messages

/inbox-check

messages = mcp__orchestrator__check_inbox(
    project_name="claude-family",  # IMPORTANT: Required to see project messages
    session_id="your-session-id",  # Optional: for direct messages
    include_broadcasts=True,        # Default: true
    include_read=False              # Default: false (only pending)
)

for msg in messages['messages']:
    print(f"From: {msg['from_session_id']}")
    print(f"Type: {msg['message_type']}")
    print(f"Subject: {msg['subject']}")
    print(f"Body: {msg['body']}")
    print(f"Priority: {msg['priority']}")

mcp__orchestrator__send_message(
    to_session_id="target-session-id",
    message_type="task_request",
    subject="Please review authentication changes",
    body="I've implemented JWT auth in src/auth.ts. Please review for security and best practices.",
    priority="normal",  # urgent | normal | low
    from_session_id="your-session-id"  # Optional
)

mcp__orchestrator__send_message(
    to_project="nimbus-user-loader",  # Any Claude working on this project will see it
    message_type="notification",
    subject="Migration completed",
    body="User data migration from legacy system complete. 1,234 users imported.",
    priority="normal"
)

mcp__orchestrator__broadcast(
    subject="New auto-apply instruction added",
    body="Added markdown.instructions.md for documentation standards. Affects all .md file edits.",
    priority="low",
    from_session_id="your-session-id"
)

/broadcast subject="New standard" body="Message here"

# Spawn agent async
task_id = mcp__orchestrator__spawn_agent_async(
    agent_type="researcher-opus",
    task=f"""
    Research authentication best practices.

    IMPORTANT: When complete, send results:
    mcp__orchestrator__send_message(
        to_project="claude-family",
        subject="Async Task Complete: {task_id}",
        body="<your findings here>"
    )
    """,
    workspace_dir="C:/Projects/claude-family"
)

# Later, check inbox for completion
messages = mcp__orchestrator__check_inbox(project_name="claude-family")
for msg in messages:
    if task_id in msg['subject']:
        print("Agent completed!")
        print(msg['body'])

mcp__orchestrator__acknowledge(
    message_id="message-uuid",
    action="read"
)

mcp__orchestrator__acknowledge(
    message_id="message-uuid",
    action="acknowledged"
)

mcp__orchestrator__acknowledge(
    message_id="message-uuid",
    action="actioned",
    project_id="project-uuid",  # Required
    priority=3  # Optional: 1-5, default 3
)

mcp__orchestrator__acknowledge(
    message_id="message-uuid",
    action="deferred",
    defer_reason="Out of scope for current sprint - will revisit in Q2"  # Required
)

Is this message actionable?
(task_request / question / handoff)
    │
    ├─ YES
    │   │
    │   ├─ Will you act on it?
    │   │   │
    │   │   ├─ YES → Use action='actioned' + project_id
    │   │   │         (Creates todo, marks as actioned)
    │   │   │
    │   │   └─ NO  → Use action='deferred' + defer_reason
    │   │             (Explicitly skipped with reason)
    │   │
    │   └─ Already completed it?
    │       └─ Use action='acknowledged'
    │          (Work done, no todo needed)
    │
    └─ NO (informational only)
        └─ Use action='read'
           (Just marking as seen)

mcp__orchestrator__reply_to(
    original_message_id="message-uuid",
    body="I've reviewed the auth changes. Looks good! Just one suggestion: add rate limiting to login endpoint.",
    from_session_id="your-session-id"
)

/team-status

sessions = mcp__orchestrator__get_active_sessions()

for session in sessions['sessions']:
    print(f"{session['identity_name']}: {session['project_name']}")
    print(f"  Session: {session['session_id']}")
    print(f"  Started: {session['session_start']}")

-- Unread messages for project
SELECT
    message_id::text,
    from_session_id::text,
    message_type,
    subject,
    body,
    priority,
    created_at
FROM claude.messages
WHERE to_project = 'claude-family'
  AND status = 'pending'
ORDER BY
    CASE priority
        WHEN 'urgent' THEN 1
        WHEN 'normal' THEN 2
        WHEN 'low' THEN 3
    END,
    created_at ASC;

-- Messages sent by me
SELECT
    to_project,
    to_session_id::text,
    subject,
    status,
    created_at
FROM claude.messages
WHERE from_session_id = 'your-session-id'::uuid
ORDER BY created_at DESC
LIMIT 20;

-- Broadcast messages
SELECT
    subject,
    body,
    created_at
FROM claude.messages
WHERE message_type = 'broadcast'
  AND created_at > NOW() - INTERVAL '7 days'
ORDER BY created_at DESC;

# Claude instance A hands off work
mcp__orchestrator__send_message(
    to_project="nimbus-import",
    message_type="handoff",
    subject="Handing off nimbus-import work",
    body="""
    I've completed the data loader infrastructure. Remaining work:
    1. Add error handling for malformed CSV
    2. Implement retry logic for API failures
    3. Add progress tracking

    Code is in src/loader.py. Tests pass but coverage only 60%.
    """,
    priority="normal"
)

# Ask for help with decision
mcp__orchestrator__send_message(
    to_project="claude-family",
    message_type="question",
    subject="Architecture decision: caching strategy",
    body="""
    Need input on caching for user data:

    Option A: Redis (fast, separate service)
    Option B: In-memory (simple, no extra dependency)
    Option C: PostgreSQL materialized views (consistent with DB)

    Current load: ~1000 users, read-heavy (90% reads)
    Preference?
    """,
    priority="normal"
)

# Regular progress updates
mcp__orchestrator__send_message(
    to_project="claude-family",
    message_type="status_update",
    subject="Weekly progress: Authentication feature",
    body="""
    Progress this week:
    - ✅ JWT token generation
    - ✅ Login/logout endpoints
    - ✅ Auth middleware
    - 🔄 Refresh token logic (70% complete)
    - ⏳ Email verification (not started)

    ETA: Complete by end of week
    Blockers: None
    """,
    priority="low"
)

# WRONG: Won't see project messages
messages = mcp__orchestrator__check_inbox()

# CORRECT: Sees project messages
messages = mcp__orchestrator__check_inbox(project_name="claude-family")