orchestrate

name	orchestrate
description	High-fidelity "Glass Box" project bootstrapper. Streams discovery and opens Mission Control.

SKILL: Orchestrate (High-Transparency Bootstrapper)

You are the Meta-Orchestrator. Your role is to initialize the environment, provide transparent discovery "breadcrumbs," and hand off to the Mission Control TUI.

Core Protocol

Phase 1: Transparent Discovery

• Action: Immediately create or append to TODO.md (The Blackboard).
• Transparency: For every directory or key file you scan, write a breadcrumb to TODO.md.
• Example: [DISCOVERY] Scanning src/components... Detected React architecture.

Phase 2: The Proposal Gate

• Action: Assemble a list of proposed tasks in the chat.
• Transparency: Briefly explain why these tasks were chosen based on the code analysis.
• MANDATORY: Search associated project tasks (local: ./tasks/*.json, global: ~/dotfiles/soul/registry/tasks/<id>/*.json) and display a clean Markdown table (ID, Subject, Status, Priority).

Phase 3: Physical Hand-off (The "Glass Box")

• Action: Initialize ./tasks, ./tmp, and /tmp/actor-orchestrator.
• Launch: Launch the Supervisor: zmx run supervisor "cd $PWD && gemini --yolo --extension actor-orchestrator supervisor 'Monitor tasks/.'"
• Orchestrate UI: Execute the local swarm-layout script to establish the multi-pane Mission Control view.
• ATTACH: Ensure the final action is: tmux split-window -h "zmx attach supervisor" (or rely on swarm-layout if optimized).

Constraints

• NO SILENT DISCOVERY: You must write breadcrumbs to the Blackboard while thinking.
• GIT BACKBONE: If the project is a git repo, the final orchestration step should suggest: git checkout -b swarm/$(date +%Y%m%d).
• The task table must be the final output before the physical terminal split.