orchestrator-investigate

Diagnose stuck orchestrator work units using status checks and log review.

3|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/netguy204/vibe-engineer --skill orchestrator-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator-investigate
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/orchestrator-investigate
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill orchestrator-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigates why an orchestrator work unit is stuck and provides a repeatable process to resolve it.

Core Features & Use Cases

  • Systematic status checks and log inspection to identify why a work unit is stuck
  • Evidence-driven diagnosis with phase and log guidance
  • Guided remediation steps to recover a stuck work unit without data loss

Quick Start

Run ve orch status and ve orch work-unit show for the target chunk, document findings, and follow the recommended remediation steps.

Frequently Asked Questions about orchestrator-investigate

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

FAQPage Schema
How do I diagnose a stuck orchestrator work unit?

To diagnose a stuck orchestrator work unit, run ve orch status and ve orch work-unit show to inspect the target chunk. Document your findings to identify the failure mode before applying remediation steps.

What causes an orchestrator work unit to enter a NEEDS_ATTENTION state?

An orchestrator work unit enters a NEEDS_ATTENTION state across common failure modes that halt progress. Systematic status checks, work-unit inspection, and log review gather evidence to identify the specific root cause.

How do I fix a stuck work unit without losing data?

Fix a stuck work unit without data loss by following guided remediation steps after evidence-driven diagnosis. This involves safe branch management and applying VE commands to recover the work unit securely.

What steps should I follow to resolve orchestrator work unit failures?

Resolve orchestrator work unit failures by performing status checks, inspecting the work unit, reviewing logs for evidence, diagnosing the root cause, and executing safe branch management using VE commands for remediation.

Do I need specific commands to troubleshoot orchestrator issues?

Yes, troubleshooting orchestrator issues requires VE commands such as ve orch status and ve orch work-unit show. These commands facilitate evidence gathering and guide the safe branch management needed for remediation.