ops-orchestrate

## Runtime Context Before orchestrating, load: 1. **Preferences**: `cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` — read `owner`, `timezone`, `yolo_enabled`, registry path 2. **Daemon health**: `cat ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json` — ensure all services healthy before dispatching 3. **Secrets**: Resolve via env → Doppler → password manager: `GITHUB_TOKEN`, `SENTRY_AUTH_TOKEN`, `LINEAR_API_KEY`, `ANTHROPIC_API_KEY` 4. **Ops memories**: Check `${CLAUDE_PLUGIN_DATA_DIR}/memories/topics_active.md` for priority context # OPS ► ORCHESTRATE — Autonomous Work Engine Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). ## Context Detection Detect where this skill was invoked: ```bash # If invoked from a specific project directory (not ~), scope to that project CWD="$(pwd)" if [ "$CWD" != "$HOME" ] && [ -d "$CWD/.git" ]; then echo "SCOPED:$CWD" else echo "GLOBAL" fi ``` - **SCOPED mode** (invoked inside a project dir): Limit work to that project only. Include all todos/tasks from the current conversation context. Skip the global registry scan. - **GLOBAL mode** (invoked from ~ or with no git repo): Scan all registered projects. If `$ARGUMENTS` contains `--project <alias>`, use SCOPED mode for that alias regard...