菜单
Use when dispatching darken spawn subharnesses or reading their committed work back from .scion/agents/<name>/workspace
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use at session start in any darken-managed workspace (any repo containing `.scion/grove-id`) to prime as the host-mode orchestrator for the §7 pipeline. Loads the non-negotiables block, the routing classifier, the background-dispatch monitoring protocol, the bounded-transcript evidence rule, the 14-role roster, the escalation classifier, and the four loop primitives for playbook-driven coordination (darken dispatch / inbox / accept / state). Invoke whenever the operator types a task and the workspace is darken-managed.
Use in any darken-managed workspace (any repo containing `.scion/grove-id`) when you would normally dispatch a subagent via the Agent tool but you are operating as the host-mode orchestrator. Translates the muscle memory into subharness dispatch, maps task shapes to roles, frames the task in caveman-standard with a status-publishing recipe and a fixed milestone vocabulary, and reads worker output back via the bounded-transcript protocol.
Constitution-driven specification flow mounted by planner-t4. Activates when an agent must drive the full ratification pipeline: constitution review, spec.md authoring, plan.md production, and tasks/ decomposition. Use when operating under the specify CLI, when a feature requires formal ratification before implementation, or when producing structured spec artifacts for downstream worker harnesses.
Multi-skill bundle mounted by planner-t3. Activates when a design session must scaffold an architecture that satisfies both Hipp zero-config reliability principles and Ousterhout deep-module complexity reduction. Triggers on requests to design libraries, data layers, or system modules where simplicity, embeddability, and minimal cognitive load must all be balanced together.
Use when designing libraries, modules, or data layers that must be simple, reliable, and self-contained. Use when choosing between embedded vs server-based solutions. Use when reviewing code for unnecessary complexity, dependencies, or configuration. Triggers on requests involving zero-config design, embedded systems, long-term maintainability, or first-principles thinking.
Use when designing modules, classes, APIs, or system architecture. Use when reviewing or refactoring code for complexity. Use when choosing between implementation approaches. Triggers on requests involving abstraction design, interface simplicity, information hiding, or reducing cognitive load.
| name | agent-worktree-discipline |
| description | Use when dispatching darken spawn subharnesses or reading their committed work back from .scion/agents/<name>/workspace |
Agent worktrees at .scion/agents/<name>/workspace/ are destroyed when the agent is deleted via scion delete <name>. Any commit that exists only in the worktree (not pushed to a remote branch) is permanently lost.
Core rule: push every commit immediately. The worktree is not durable storage.
Brief every dispatched implementer with: push to a feature branch after every commit. Single-commit-per-task with git push origin feat/<branch> between commits. Never accumulate uncommitted or unpushed work.
Never scion delete <agent> until you have verified the agent's commits exist on origin. Run git fetch origin <branch>; git log --oneline main..origin/<branch> and confirm the SHAs match what you expect before deletion.
Use git -C <absolute-path> instead of cd when inspecting agent worktrees. A cd into the worktree shifts the orchestrator's cwd into a different git repo (the worktree has a token-embedded clone URL different from the host repo), and subsequent commands target the wrong repo. Lost an entire PR cycle to this in the v0.1.16 push attempt.
Cherry-pick from worktree before delete if not pushed. git fetch /absolute/path/to/.scion/agents/<name>/workspace <branch>; git cherry-pick FETCH_HEAD preserves authorship.
scion delete impl-1 -y was run — all 3 commits irrecoverable. Bug #18 in v0.1.18 backlog (preserve-on-delete) addresses this at substrate level; until landed, push-as-you-go is mandatory.cd .scion/agents/.../workspace followed by git push -u origin <branch> wrote to the worktree's remote (which had a different URL); subsequent gh pr create from the orchestrator dir picked the wrong default repo, returning a confusing error. git -C <path> would have prevented it.After EACH commit, run git push origin <feature-branch> immediately.
Never accumulate uncommitted work or unpushed commits.
If budget runs out, push what you have before terminating.