nexus-orchestrator

Orchestrate a complex task using atomic subagent execution with verification

Process ideas from the inbox - triage, evaluate, integrate or archive

Execute atomic tasks with full observability. Returns structured YAML with understood/approach/observations/blockers/output/confidence/evidence. Use for isolated task execution where you need deterministic, verifiable behavior.

Two-stage code review agent. Stage 1 checks spec compliance, Stage 2 checks code quality. Stage 2 is BLOCKED until Stage 1 passes. Use after implementation to validate work.

Use when entering an unfamiliar codebase, starting a new feature, or before any implementation task. Provides structured exploration protocol to understand before acting.

Use when tasks fail due to transient errors. Provides structured retry strategies and graceful degradation patterns. Invoke on network errors, rate limits, or intermittent failures.

Use before committing to a task. Provides complexity analysis and scope assessment. Invoke when user asks "how complex" or before large features.

Use when all tasks are complete. Presents completion options and enforces test gate. Work is never left in limbo.

This skill should be used when orchestrating complex tasks, decomposing work into atomic units, dispatching to subagents, verifying outputs, or when discussing task verification and deviation tracking patterns.

Use when facing multiple tasks or failures. Provides decision framework for concurrent vs sequential execution. Invoke before dispatching multiple subagents.

Invoke when debugging failures. MANDATORY when 3+ fix attempts have failed. Enforces root cause investigation before fixes.

Use for any code implementation task. Enforces RED-GREEN-REFACTOR cycle. "If you didn't watch it fail, you don't know if it tests the right thing."

This skill MUST be invoked before any completion claim, success report, or task transition. Mandates 5-step evidence protocol. Use when about to claim "done", "complete", "working", "fixed", or any success state.

Use when creating implementation plans. Mandates exact file paths, complete code samples, and expected output. No vague language allowed.

4 hooks across 4 events