DeepSeek Harness CLI Orchestrator - Cross-AI Task Delegation
Experimental executor kind. LLM Gateway deepseek-v4.1-flash-1017 is verified on dsh
0.2.2-rc.3 (2026-11-14) and is the default route. OpenCode Go deepseek-v4.1-flash was
proven on 2026-11-07 with an API key against https://opencode.ai/zen/go/v1 and stays out
of defaults.
Orchestrate DeepSeek Harness (dsh, npm @deepseek-ai/dsh) for one-task headless runs: a read-only review, a single scoped implementation or an independent second opinion, with the model fixed by a checked-in route patch.
The offline contract pin is the source for every flag and failure shape: contract pin evidence.
Each live result applies only to the route and behavior the saved probe exercised. Keep every behavior outside the saved probes marked UNKNOWN with the reason.
Core principle: the harness owns model selection, so the caller owns composition. Every dispatch names exactly one roster route patch, the lineage patch and the guards patch, runs from a scratch cwd with a disposable DSH_HOME, and counts as complete only on exit 0 plus a completed final event.
1. WHEN TO USE
Activation Triggers
- Explicit dsh dispatch: the task names DeepSeek Harness,
dsh or dsh headless.
- Cross-AI validation: an independent review or second opinion from a DeepSeek V4.1 Flash run that is not the calling runtime.
- One-task headless work: a bounded task that answers once and exits, with a machine-readable JSON event stream.
- Composition checks: proving the route, lineage and guards patches compose with
--dump-config before any model call.
When NOT to Use
dsh is not on PATH, or dsh --version is not the pinned version.
- The task needs a model outside the two-route roster, a GLM or official DeepSeek route, or a provider the roster does not list.
- The task needs an interactive session, a human answer mid-run, plan mode or native goal rounds.
- The task requires OpenCode Go and
OPENCODE_API_KEY is not set.
- The only cwd available is the repository root.
2. SMART ROUTING
The cli-external-orchestration hub routes a dsh dispatch here when the request names DeepSeek Harness, dsh, dsh headless or says "delegate to dsh". LLM Gateway is verified. OpenCode Go is proven on 2026-11-07 with an API key against https://opencode.ai/zen/go/v1.
command -v dsh and the pinned dsh --version decide whether a local dispatch can run, and both run before every dispatch.
Every run loads references/cli-reference.md and assets/prompt-quality-card.md first, before any intent selection.
Read ROUTER.md before selecting skill-local resources, and open only the matched files.
3. HOW IT WORKS
Execution Ownership
This packet owns the dispatch contract: the hard rules, the roster, the argv shape and the prompt mechanics.
For research and review lineages, the shared deep-loop runtime owns process construction through the experimental cli-deepseek-harness executor kind, described in fanout-executor.md. The verified LLM Gateway route is the default. OpenCode Go is proven on 2026-11-07 with an API key against https://opencode.ai/zen/go/v1 and remains explicit-only.
Do not add a packet-local wrapper, spawn path or command builder.
Closed roster: non-roster routes are FORBIDDEN. Two routes exist, LLM Gateway and OpenCode Go, both serving DeepSeek V4.1 Flash. Mistral work goes through cli-mistral-vibe, not dsh. providers-and-models.md section 2 is the one place the ids, endpoints and key variables are recorded. dsh validates no catalog membership, so a patch naming any other model would run. The preflight is the only gate.
The Dispatch Shape
cd "$RUN_DIR" && printf '%s' "$PROMPT" | DSH_HOME="$RUN_DIR/.dsh-home" \
dsh --profile headless --patch "$REPO/.dsh/patches/route-llmgateway-deepseek.patch.yml" --patch "$REPO/.dsh/patches/lineage.patch.yml" \
--patch "$REPO/.dsh/patches/guards.patch.yml" \
--json --permission-mode read-only --approval-policy never -
$RUN_DIR is a fresh scratch directory and $REPO is the checkout root, so all three patches are named by absolute path. Swap the route file for route-opencode-go-deepseek.patch.yml to use the other roster route. Name each patch by its literal file name: the preflight checks the roster from that name, and a patch hidden behind a variable fails route-patch-required. A writer uses workspace-write and names any directory it must write outside the cwd with --add-dir. The annotated shape and every flag are in cli-reference.md sections 3 to 5.
Dispatch Lifecycle
- Create the scratch cwd and set
DSH_HOME inside it.
- Run
command -v dsh and dsh --version </dev/null, and refuse anything but the pin in cli-reference.md section 2.
- Pick exactly one route patch from the roster, then check that it, the lineage patch and the guards patch exist.
- Compose the prompt with prompt-quality-card.md and a template from prompt-templates.md.
- Pipe the prompt to the dispatch shape, keeping stdout, stderr and the exit code apart.
- Validate exit 0 and a last
final event with reason.kind completed, then check the diff and the tests.
Dispatch-Critical Gotchas
- No model, provider, reasoning, cwd or timeout option exists. dsh headless takes only
--json, --session-id, --permission-mode, --approval-policy and --add-dir. A Pi or OpenCode flag is not a dsh option. Route and model come from the route patch, and the caller owns the time bound.
- A missing route patch reaches the official DeepSeek API. The default composition names provider
deepseek-official. It is never a roster route.
- The repository root leaks keys. Headless reads keys from the environment, then
<cwd>/.env, then $DSH_HOME/.env, and the root holds a .env. The session event's cwd field shows where a run started.
- A well-formed stream can be a failure. Observed keyless: exit 1, and the last line is a valid
final event with reason.kind error and code MISSING_CREDENTIAL. Read both the exit code and the reason.
- First boot writes into the resolved home. A profile-scoped command, even
--help, initializes profile files. An unset DSH_HOME means ~/.dsh.
- Approvals default to
ask. read-only and workspace-write both ask, and a headless run has no one to answer, so --approval-policy never is mandatory. It rejects calls and confines nothing.
Provider Preflight
A missing key fails fast and cheaply: the keyless offline run exited 1 with MISSING_CREDENTIAL naming the route's key variable on stderr. Surface that variable name to the operator and stop. Never pass a key in a prompt or write one into the checkout.
4. RULES
The thirteen fail-closed rules live in hard-rules.json: headless-only, stdin-dash-required, route-patch-required, closed-roster, approval-never-required, dsh-home-isolated, lineage-patch-required, guards-patch-required, json-final-and-exit-required, pinned-version-required, dsh-availability-required, no-repo-root-dotenv and mcp-opt-in-only.
✅ ALWAYS
- Run
command -v dsh and the pinned version probe before every dispatch.
- Dispatch
dsh --profile headless with the prompt on stdin after a lone -.
- Pass exactly one roster route patch, the lineage patch and the guards patch, by absolute path, before the app options.
- For a single dispatch, set
DSH_HOME to a fresh directory and use a scratch cwd outside the checkout. Deep-loop fan-out is the exception: each lineage runs with cwd set to its lineage directory and a disposable DSH_HOME under the OS temp directory.
- Pass
--json and --approval-policy never, and pick read-only or workspace-write deliberately.
- Count a run complete only on exit 0 and a last
final event whose reason.kind is completed.
- Compose every dispatch as
{resolved agent persona + task prompt}, inlining the persona block, because dsh has no agent-file loader. Canonical contract: ../../sk-prompt/assets/cli-prompt-quality-card.md "Persona Injection".
- Set
AI_SESSION_CHILD=1 in the child's environment and copy the preamble from shared/references/child-dispatch-preamble.md to the top of the prompt.
- Give a build dispatch one change per brief: the file, the edit and the check that proves it.
- Keep route status specific: LLM Gateway is verified, OpenCode Go is proven on 2026-11-07 with an API key against
https://opencode.ai/zen/go/v1, and unresolved behaviors remain UNKNOWN with their evidence gap.
⛔ NEVER
- Never dispatch any route outside the two-route roster, and never write a route patch for one.
- Never start dsh with the repository root as its cwd.
- Never run any dsh command with
DSH_HOME unset.
- Never use
danger-full-access, and never treat --approval-policy never as confinement.
- Never mount MCP without the dedicated MCP patch, and never for a task that names no MCP tool.
- Never put a key,
.env content or a credential value in a prompt, a patch or a file in the checkout.
- Never pass
DEEPSEEK_API_KEY to a dispatch. It switches the official web search and fetch route back on.
- Never pin a dist-tag. Pin the literal version and integrity.
- Never dispatch dsh from inside a dsh child or a fan-out lineage.
- Never build a second dsh adapter inside this packet.
⚠️ ESCALATE IF
dsh is missing from PATH or reports a version other than the pin.
- The task needs a keyed dispatch and the route's key variable is not set.
- A
--dump-config run prints any stderr line, which can mean a patch target row was renamed.
- The task needs the OpenCode Go route on a provider endpoint other than
https://opencode.ai/zen/go/v1.
- The task depends on behavior still marked UNKNOWN.
5. REFERENCES
Core References
- cli-reference.md - The version pin, the headless option set, the launcher flags, the dispatch shape and the exit contract
- providers-and-models.md - The closed two-route roster, the route patch shape and what stays unconfirmed
- runtime-folder-and-sync.md - The
.dsh/ folder, DSH_HOME isolation, skills, prompts and personas
- guards-and-hooks.md - Harness seams, the repo-guards plugin bundle and the port table
- mcp.md - MCP off by default and the opt-in Code Mode patch
- fanout-executor.md - The experimental executor kind, its lineage command and env allowlist
- repin-runbook.md - Repeat route, confinement, reasoning and lineage probes after an rc bump
Templates and Assets
External Sources
6. SUCCESS CRITERIA
Dispatch Completion
dsh is on PATH at the pinned version before launch.
- The argv carries the headless profile, one roster route patch, the lineage patch, the guards patch,
--json, --approval-policy never and a lone -.
- The run started from a scratch cwd with a disposable
DSH_HOME.
- Exit 0 and a last
final event with reason.kind completed, and the workspace changes pass the caller's verification gates.
Packet Quality
- Every flag the references name appears in the captured help text or in the launcher table that grounds it separately.
- LLM Gateway is listed as verified, OpenCode Go as proven on 2026-11-07 with an API key against
https://opencode.ai/zen/go/v1, and every remaining UNKNOWN has a reason.
- No nested advisor identity is introduced under this packet.
7. INTEGRATION POINTS
Hub Integration
The hub owns advisor identity, mode registration and router policy. This packet owns only the dsh dispatch contract, and it must not add description.json or graph-metadata.json. The hub already registers and routes this mode, and the shared runtime carries its executor kind. LLM Gateway is verified. OpenCode Go is proven on 2026-11-07 with an API key against https://opencode.ai/zen/go/v1.
Deep-Loop Integration
The shared runtime is the sole process adapter for lineages. This packet supplies the rules, the roster and the prompt mechanics.
Code and Spec Integration
sk-code owns code verification. system-spec-kit owns Gate 3, spec folders and continuity. Name the established spec folder in a delegated prompt when the parent workflow has one.
Tool Roles
- Bash runs the probes, the composition check and the dispatch.
- Read, Glob and Grep inspect prompts, references, the event stream and returned changes.
- This packet grants no new external tools.
8. REFERENCES AND RELATED RESOURCES
Start with the CLI reference and the prompt-quality card, then load only the references matching the task. The router discovers markdown resources inside this packet.
Related skills: cli-pi, cli-opencode, cli-claude-code, cli-codex, cli-cursor and cli-devin for sibling CLI dispatch, sk-code for code standards, system-deep-loop for lineage execution and system-spec-kit for packet handback.
1---2name: cli-deepseek-harness3description: "DeepSeek Harness (dsh) CLI executor for pinned headless one-task dispatch over a closed two-route DeepSeek V4.1 Flash roster."4allowed-tools: [Bash, Read, Glob, Grep]5version: 1.0.2.06metadata:7 source: https://skillmd.com/skills/michelkerkmeester/cli-deepseek-harness8---910# DeepSeek Harness CLI Orchestrator - Cross-AI Task Delegation1112> **Experimental executor kind.** LLM Gateway `deepseek-v4.1-flash-1017` is verified on dsh13> 0.2.2-rc.3 (2026-11-14) and is the default route. OpenCode Go `deepseek-v4.1-flash` was14> proven on 2026-11-07 with an API key against `https://opencode.ai/zen/go/v1` and stays out15> of defaults.1617Orchestrate DeepSeek Harness (`dsh`, npm `@deepseek-ai/dsh`) for one-task headless runs: a read-only review, a single scoped implementation or an independent second opinion, with the model fixed by a checked-in route patch.18The offline contract pin is the source for every flag and failure shape: [contract pin evidence](../../../../specs/cli-external-orchestration/runtime-lifecycle/002-cli-deepseek-harness-creation/002-dsh-offline-contract-pin/evidence/headless-help.txt).19Each live result applies only to the route and behavior the saved probe exercised. Keep every behavior outside the saved probes marked UNKNOWN with the reason.2021**Core principle**: the harness owns model selection, so the caller owns composition. Every dispatch names exactly one roster route patch, the lineage patch and the guards patch, runs from a scratch cwd with a disposable `DSH_HOME`, and counts as complete only on exit 0 plus a `completed` final event.2223---2425## 1. WHEN TO USE2627### Activation Triggers2829- **Explicit dsh dispatch**: the task names DeepSeek Harness, `dsh` or `dsh headless`.30- **Cross-AI validation**: an independent review or second opinion from a DeepSeek V4.1 Flash run that is not the calling runtime.31- **One-task headless work**: a bounded task that answers once and exits, with a machine-readable JSON event stream.32- **Composition checks**: proving the route, lineage and guards patches compose with `--dump-config` before any model call.3334### When NOT to Use3536- `dsh` is not on PATH, or `dsh --version` is not the pinned version.37- The task needs a model outside the two-route roster, a GLM or official DeepSeek route, or a provider the roster does not list.38- The task needs an interactive session, a human answer mid-run, plan mode or native goal rounds.39- The task requires OpenCode Go and `OPENCODE_API_KEY` is not set.40- The only cwd available is the repository root.4142---4344## 2. SMART ROUTING4546The `cli-external-orchestration` hub routes a dsh dispatch here when the request names DeepSeek Harness, `dsh`, `dsh headless` or says "delegate to dsh". LLM Gateway is verified. OpenCode Go is proven on 2026-11-07 with an API key against `https://opencode.ai/zen/go/v1`.47`command -v dsh` and the pinned `dsh --version` decide whether a local dispatch can run, and both run before every dispatch.48Every run loads `references/cli-reference.md` and `assets/prompt-quality-card.md` first, before any intent selection.49Read [`ROUTER.md`](./ROUTER.md) before selecting skill-local resources, and open only the matched files.5051---5253## 3. HOW IT WORKS5455### Execution Ownership5657This packet owns the dispatch contract: the hard rules, the roster, the argv shape and the prompt mechanics.58For research and review lineages, the shared deep-loop runtime owns process construction through the experimental `cli-deepseek-harness` executor kind, described in [fanout-executor.md](./references/fanout-executor.md). The verified LLM Gateway route is the default. OpenCode Go is proven on 2026-11-07 with an API key against `https://opencode.ai/zen/go/v1` and remains explicit-only.59Do not add a packet-local wrapper, spawn path or command builder.6061**Closed roster: non-roster routes are FORBIDDEN.** Two routes exist, LLM Gateway and OpenCode Go, both serving DeepSeek V4.1 Flash. Mistral work goes through `cli-mistral-vibe`, not dsh. [providers-and-models.md](./references/providers-and-models.md) section 2 is the one place the ids, endpoints and key variables are recorded. dsh validates no catalog membership, so a patch naming any other model would run. The preflight is the only gate.6263### The Dispatch Shape6465```bash66cd "$RUN_DIR" && printf '%s' "$PROMPT" | DSH_HOME="$RUN_DIR/.dsh-home" \67 dsh --profile headless --patch "$REPO/.dsh/patches/route-llmgateway-deepseek.patch.yml" --patch "$REPO/.dsh/patches/lineage.patch.yml" \68 --patch "$REPO/.dsh/patches/guards.patch.yml" \69 --json --permission-mode read-only --approval-policy never -70```7172`$RUN_DIR` is a fresh scratch directory and `$REPO` is the checkout root, so all three patches are named by absolute path. Swap the route file for `route-opencode-go-deepseek.patch.yml` to use the other roster route. Name each patch by its literal file name: the preflight checks the roster from that name, and a patch hidden behind a variable fails `route-patch-required`. A writer uses `workspace-write` and names any directory it must write outside the cwd with `--add-dir`. The annotated shape and every flag are in [cli-reference.md](./references/cli-reference.md) sections 3 to 5.7374### Dispatch Lifecycle75761. Create the scratch cwd and set `DSH_HOME` inside it.772. Run `command -v dsh` and `dsh --version </dev/null`, and refuse anything but the pin in [cli-reference.md](./references/cli-reference.md) section 2.783. Pick exactly one route patch from the roster, then check that it, the lineage patch and the guards patch exist.794. Compose the prompt with [prompt-quality-card.md](./assets/prompt-quality-card.md) and a template from [prompt-templates.md](./assets/prompt-templates.md).805. Pipe the prompt to the dispatch shape, keeping stdout, stderr and the exit code apart.816. Validate exit 0 and a last `final` event with `reason.kind` `completed`, then check the diff and the tests.8283### Dispatch-Critical Gotchas8485- **No model, provider, reasoning, cwd or timeout option exists.** dsh headless takes only `--json`, `--session-id`, `--permission-mode`, `--approval-policy` and `--add-dir`. A Pi or OpenCode flag is not a dsh option. Route and model come from the route patch, and the caller owns the time bound.86- **A missing route patch reaches the official DeepSeek API.** The default composition names provider `deepseek-official`. It is never a roster route.87- **The repository root leaks keys.** Headless reads keys from the environment, then `<cwd>/.env`, then `$DSH_HOME/.env`, and the root holds a `.env`. The `session` event's `cwd` field shows where a run started.88- **A well-formed stream can be a failure.** Observed keyless: exit 1, and the last line is a valid `final` event with `reason.kind` `error` and code `MISSING_CREDENTIAL`. Read both the exit code and the reason.89- **First boot writes into the resolved home.** A profile-scoped command, even `--help`, initializes profile files. An unset `DSH_HOME` means `~/.dsh`.90- **Approvals default to `ask`.** `read-only` and `workspace-write` both ask, and a headless run has no one to answer, so `--approval-policy never` is mandatory. It rejects calls and confines nothing.9192### Provider Preflight9394A missing key fails fast and cheaply: the keyless offline run exited 1 with `MISSING_CREDENTIAL` naming the route's key variable on stderr. Surface that variable name to the operator and stop. Never pass a key in a prompt or write one into the checkout.9596---9798## 4. RULES99100The thirteen fail-closed rules live in [hard-rules.json](./hard-rules.json): `headless-only`, `stdin-dash-required`, `route-patch-required`, `closed-roster`, `approval-never-required`, `dsh-home-isolated`, `lineage-patch-required`, `guards-patch-required`, `json-final-and-exit-required`, `pinned-version-required`, `dsh-availability-required`, `no-repo-root-dotenv` and `mcp-opt-in-only`.101102### ✅ ALWAYS1031041. Run `command -v dsh` and the pinned version probe before every dispatch.1052. Dispatch `dsh --profile headless` with the prompt on stdin after a lone `-`.1063. Pass exactly one roster route patch, the lineage patch and the guards patch, by absolute path, before the app options.1074. For a single dispatch, set `DSH_HOME` to a fresh directory and use a scratch cwd outside the checkout. Deep-loop fan-out is the exception: each lineage runs with `cwd` set to its lineage directory and a disposable `DSH_HOME` under the OS temp directory.1085. Pass `--json` and `--approval-policy never`, and pick `read-only` or `workspace-write` deliberately.1096. Count a run complete only on exit 0 and a last `final` event whose `reason.kind` is `completed`.1107. Compose every dispatch as `{resolved agent persona + task prompt}`, inlining the persona block, because dsh has no agent-file loader. Canonical contract: `../../sk-prompt/assets/cli-prompt-quality-card.md` "Persona Injection".1118. Set `AI_SESSION_CHILD=1` in the child's environment and copy the preamble from [`shared/references/child-dispatch-preamble.md`](../shared/references/child-dispatch-preamble.md) to the top of the prompt.1129. Give a build dispatch one change per brief: the file, the edit and the check that proves it.11310. Keep route status specific: LLM Gateway is verified, OpenCode Go is proven on 2026-11-07 with an API key against `https://opencode.ai/zen/go/v1`, and unresolved behaviors remain UNKNOWN with their evidence gap.114115### ⛔ NEVER1161171. Never dispatch any route outside the two-route roster, and never write a route patch for one.1182. Never start dsh with the repository root as its cwd.1193. Never run any dsh command with `DSH_HOME` unset.1204. Never use `danger-full-access`, and never treat `--approval-policy never` as confinement.1215. Never mount MCP without the dedicated MCP patch, and never for a task that names no MCP tool.1226. Never put a key, `.env` content or a credential value in a prompt, a patch or a file in the checkout.1237. Never pass `DEEPSEEK_API_KEY` to a dispatch. It switches the official web search and fetch route back on.1248. Never pin a dist-tag. Pin the literal version and integrity.1259. Never dispatch dsh from inside a dsh child or a fan-out lineage.12610. Never build a second dsh adapter inside this packet.127128### ⚠️ ESCALATE IF1291301. `dsh` is missing from PATH or reports a version other than the pin.1312. The task needs a keyed dispatch and the route's key variable is not set.1323. A `--dump-config` run prints any stderr line, which can mean a patch target row was renamed.1334. The task needs the OpenCode Go route on a provider endpoint other than `https://opencode.ai/zen/go/v1`.1345. The task depends on behavior still marked UNKNOWN.135136---137138## 5. REFERENCES139140### Core References141142- [cli-reference.md](./references/cli-reference.md) - The version pin, the headless option set, the launcher flags, the dispatch shape and the exit contract143- [providers-and-models.md](./references/providers-and-models.md) - The closed two-route roster, the route patch shape and what stays unconfirmed144- [runtime-folder-and-sync.md](./references/runtime-folder-and-sync.md) - The `.dsh/` folder, `DSH_HOME` isolation, skills, prompts and personas145- [guards-and-hooks.md](./references/guards-and-hooks.md) - Harness seams, the repo-guards plugin bundle and the port table146- [mcp.md](./references/mcp.md) - MCP off by default and the opt-in Code Mode patch147- [fanout-executor.md](./references/fanout-executor.md) - The experimental executor kind, its lineage command and env allowlist148- [repin-runbook.md](./references/repin-runbook.md) - Repeat route, confinement, reasoning and lineage probes after an rc bump149150### Templates and Assets151152- [prompt-quality-card.md](./assets/prompt-quality-card.md) - Thin delegator to the canonical prompt-models card, plus dsh addenda153- [prompt-templates.md](./assets/prompt-templates.md) - Preflight, dry composition check, review, implementation, validation and handback154155### External Sources156157- [Offline contract pin evidence](../../../../specs/cli-external-orchestration/runtime-lifecycle/002-cli-deepseek-harness-creation/002-dsh-offline-contract-pin/evidence/headless-help.txt) - The captured headless help, with version, dump-config and keyless captures beside it158- [Research synthesis](../../../../specs/cli-external-orchestration/runtime-lifecycle/002-cli-deepseek-harness-creation/001-deep-research/research/research.md) - The source-backed design behind every rule159160---161162## 6. SUCCESS CRITERIA163164### Dispatch Completion165166- `dsh` is on PATH at the pinned version before launch.167- The argv carries the headless profile, one roster route patch, the lineage patch, the guards patch, `--json`, `--approval-policy never` and a lone `-`.168- The run started from a scratch cwd with a disposable `DSH_HOME`.169- Exit 0 and a last `final` event with `reason.kind` `completed`, and the workspace changes pass the caller's verification gates.170171### Packet Quality172173- Every flag the references name appears in the captured help text or in the launcher table that grounds it separately.174- LLM Gateway is listed as verified, OpenCode Go as proven on 2026-11-07 with an API key against `https://opencode.ai/zen/go/v1`, and every remaining UNKNOWN has a reason.175- No nested advisor identity is introduced under this packet.176177---178179## 7. INTEGRATION POINTS180181### Hub Integration182183The hub owns advisor identity, mode registration and router policy. This packet owns only the dsh dispatch contract, and it must not add `description.json` or `graph-metadata.json`. The hub already registers and routes this mode, and the shared runtime carries its executor kind. LLM Gateway is verified. OpenCode Go is proven on 2026-11-07 with an API key against `https://opencode.ai/zen/go/v1`.184185### Deep-Loop Integration186187The shared runtime is the sole process adapter for lineages. This packet supplies the rules, the roster and the prompt mechanics.188189### Code and Spec Integration190191sk-code owns code verification. system-spec-kit owns Gate 3, spec folders and continuity. Name the established spec folder in a delegated prompt when the parent workflow has one.192193### Tool Roles194195- Bash runs the probes, the composition check and the dispatch.196- Read, Glob and Grep inspect prompts, references, the event stream and returned changes.197- This packet grants no new external tools.198199---200201## 8. REFERENCES AND RELATED RESOURCES202203Start with the CLI reference and the prompt-quality card, then load only the references matching the task. The router discovers markdown resources inside this packet.204205Related skills: cli-pi, cli-opencode, cli-claude-code, cli-codex, cli-cursor and cli-devin for sibling CLI dispatch, sk-code for code standards, system-deep-loop for lineage execution and system-spec-kit for packet handback.