using-specialists-v2

Specialist workflows use bead-first orchestration to define complete task contracts before dispatching, ensuring clear scope, validation, and safe merge discipline for code review and debugging tasks.

Bead-driven task planning turns ambiguous tasks into complete execution contracts that specify specialist selection, context management, and worktree handling before multi-chain project coordination begins.

Manage isolated specialist execution by handling worktrees, job reuse, and context depth, applying safe merge or recovery paths to prevent context loss during complex implementation flows.

Yes, you can chain explorer, executor, reviewer, test, and recovery specialists to run feature implementation from task definition through testing to final publication without losing context.

Specialist orchestration applies to documentation sync and testing workflows by coordinating specialist chains that validate and merge updates while maintaining strict context management and recovery discipline.

Avoid bead-first orchestration for simple, single-step tasks that do not require specialist selection, worktree isolation, or safe merge recovery discipline to complete successfully.