メニュー
Use when composing the brief argument passed to darken spawn or scion message; the brief flows through scion sh -c wrapper that misparses three ASCII characters
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 | shell-safe-briefs |
| description | Use when composing the brief argument passed to darken spawn or scion message; the brief flows through scion sh -c wrapper that misparses three ASCII characters |
Scion's harness layer wraps the agent invocation in sh -c "tmux ... claude --system-prompt \"...\" \"<TASK>\"". The TASK arg lives inside double quotes. Three ASCII characters break the outer quoting and cause the agent to crash at boot with Syntax error: end of file unexpected or Syntax error: word unexpected:
| Character | Effect inside "..." |
|---|---|
' (U+0027 apostrophe) | Closes the outer single-quoted shell argument when embedded |
" (U+0022 double quote) | Closes the outer double-quoted shell argument |
` (U+0060 backtick) | Triggers command substitution |
Tracked upstream as bug #15 (scion harness shell-escaping). Until fixed in scion, every brief composed by this orchestrator must use Unicode equivalents at compose time.
bin/darken spawn ... "<brief>" callscion message <agent> "<message>" callscion message --broadcast "<message>" call.scion/templates/<role>/system-prompt.md or agents.mdUse these Unicode equivalents — read identically to humans and to LLMs but are not shell-special:
| ASCII | Unicode | Looks like |
|---|---|---|
' U+0027 | ' U+2019 | Right single quotation mark |
" U+0022 | " U+201C / " U+201D | Curly quotes (paired) |
` U+0060 | ' U+2019 | Lose backtick formatting; use prose |
Or restructure the prose to avoid them:
cmd/darken/spawn.go as cmd/darken/spawn.godon't, planner's); spawn crashed with Syntax error: end of file unexpected. Cleared via scion delete, three retries with progressive sanitization required (apostrophes → double quotes → backticks).Before any spawn or message call, scan the brief text for ', ", `. If present, apply Unicode replacement. One bash heuristic to verify:
echo "$BRIEF" | grep -cE "['\"\`]"
# If output > 0, sanitize before sending