team-mode-orchestration-verification

Verify team-mode task completion using filesystem artifacts and task files.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill team-mode-orchestration-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-mode-orchestration-verification
Source: https://github.com/cajias/claude-skills/tree/main/plugins/cc-authoring/skills/team-mode-orchestration-verification
Command: npx skills add https://github.com/cajias/claude-skills --skill team-mode-orchestration-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid false alarms when team-mode work appears missing, incomplete, or silent by checking ground truth before assuming a teammate failed.

Core Features & Use Cases

  • Ground-truth verification: Confirms work through filesystem artifacts, external system state, and team task files rather than relying on protocol state alone.
  • Silent completion handling: Distinguishes between a teammate that truly stopped and one that finished correctly but failed to send a final message.
  • Safe orchestration: Prevents redundant re-dispatches, duplicate work, and collision-prone retries in Claude Code team mode.
  • Use case: A teammate sends only idle notifications after being assigned a task, and you need to verify whether the expected file, git state, or external resource was actually created.

Quick Start

Verify the expected artifact and team task state first, and only re-dispatch if the work is truly incomplete.

Frequently Asked Questions about team-mode-orchestration-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Claude Code teammate work when task visibility is misleading?

Verify teammate work by checking filesystem artifacts, external system state, and team task files before trusting protocol state. This confirms whether the expected output was actually created despite misleading task visibility.

Why does a teammate send idle notifications after being assigned a task in team mode?

Idle notifications often occur when a teammate finishes correctly but fails to send a final completion message. Silent completion handling distinguishes between a teammate that truly stopped and one that completed work without replying.

How do I prevent redundant re-dispatches in Claude Code orchestration?

Prevent redundant re-dispatches by verifying ground truth through filesystem artifacts and git state before retrying. Safe orchestration checks confirm work is truly incomplete before triggering collision-prone duplicate tasks.

Can I check git state and filesystem artifacts before re-dispatching team mode tasks?

Yes, you can check git state, filesystem artifacts, and external system state to verify team task completion. Ground-truth verification confirms whether expected files or resources were created before you re-dispatch.

What are the limitations of trusting protocol state for Claude Code task completion?

Relying solely on protocol state can trigger false alarms when work appears missing or silent. Limitations include missing final messages and misleading task visibility, requiring ground-truth checks before assuming failure.