spectra

<!-- 🔒 LOCKED — managed by clade Source: plugins/hub-core/skills/spectra/ Edit at: $CLADE_HOME Local edits will be reverted by the next sync. --> # Spectra Orchestrator When the user invokes `/spectra` without specifying a sub-skill, act as the orchestrator that determines the right workflow phase. ## Decision Flow Run through these steps **in order**. Stop at the first match. ### Step 1: Check active changes ```bash spectra list --json ``` Parse the result. Branch on the number of active changes: - **No active changes** → go to Step 2 (no work in progress) - **One or more active changes** → go to Step 3 (work exists) ### Step 2: No active changes — New work or inquiry Ask the user what they want to do. Use **AskUserQuestion** with these options: 1. **提案（Propose）** — 我有新功能/改動想規劃 → invoke `/spectra-propose` 2. **討論（Discuss）** — 我想先釐清需求再決定做法 → invoke `/spectra-discuss` 3. **查詢（Ask）** — 我想查詢現有 spec 的內容 → invoke `/spectra-ask` 4. **除錯（Debug）** — 我遇到問題想系統性排查 → invoke `/spectra-debug` After the user picks, invoke the corresponding skill with the Skill tool. > **Note**：選到 `Propose` 時，`spectra-propose` 入口的 Step 0 會再問一次「A. Codex GPT-5.6-sol max / B. Claude Code 繼續做」。orchestrator **不要**在這裡先問，避免雙重詢問。 ### Step 3: Active changes exist — Determine next action For each active change, run: ```bash spectra status --change "<name>" --json ``` Summarize the state to the user: ``` 📋 目前進行中的 change： - <name>: <status summary> (e.g., "proposal ✓, tasks ✓, 3/8 tasks done") ``` ...