菜单
Scaffold deterministic fake CLI executables and pytest fixtures that stand in for the real Codex/Claude binaries in provider integration tests. Use when adding integration coverage for a provider adapter, the router, or the pipeline (phases 2–5) — success and every infrastructure failure scenario.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Implement a task in wastech-orchestrator end to end — a backlog ADR (docs/backlog/), a follow-up, or a free-form request — driving it through the project's own workflow (understand → shape → plan → build → check → sync docs → review → commit) while enforcing the hard invariants. Use when the user says "implement X", "build the ADR for Y", "do the backlog item Z", or hands you a task to carry out in this repo. Orchestrates the sibling skills (/clarify-task, /assess-refactor, /simplify-task, /run-checks, /sync-docs, /simplify-review); it does not replace them.
After a behavior/CLI/config/architecture change in wastech-orchestrator, bring the docs and the follow-ups tracker in sync with the code. Use after implementing a change (the Stop docs-sync gate reminds you), before a commit, or whenever the docs no longer match the code.
Write or revise a single flow node's role prompt (`role_file`) for wastech-orchestrator — the Markdown text that becomes that node's instructions — honoring the node's typed output contract and the `{name}` variable allowlist. Use when you want to change what a step says without changing the graph; author a whole new flow with worc-flow, or repoint a step's provider/model with worc-flow-tune.
Author a new custom flow for wastech-orchestrator — a validated graph of typed nodes saved as `.worc/flows/<task_type>.yaml` with its own prompt folder, that a task selects by `task_type`. Use when you need different steps, a different output kind, or a different route than a built-in flow gives you — not to change what one step says (that is worc-flow-role) or which model a step uses (that is worc-flow-tune).
Tune an existing wastech-orchestrator flow's per-node execution knobs — which `provider`/`model`/`reasoning` a step runs on, plus `timeout_seconds`, `network_access`, `extra_args`, and the flow's loop `budgets` — without changing the graph or the prompts. Use when a step should run on a different provider or effort; author a new flow with worc-flow, or reword a step with worc-flow-role.
Build or revise a wastech-orchestrator `config.yaml` for a specific repository. Use when an operator wants help choosing providers, checks.command_sets, Git publishing, Telegram, or safe defaults for their repo, and wants a ready-to-edit config with the orchestrator's security invariants preserved.
基于 SOC 职业分类
| name | fake-cli |
| description | Scaffold deterministic fake CLI executables and pytest fixtures that stand in for the real Codex/Claude binaries in provider integration tests. Use when adding integration coverage for a provider adapter, the router, or the pipeline (phases 2–5) — success and every infrastructure failure scenario. |
Create stub "CLI" executables and the pytest plumbing that point a provider's command at them, so integration tests exercise the adapters/router/pipeline without the real Codex or Claude — no network, fully deterministic (testing.md).
Map each to a normalized ErrorClass (spec §7.1) so the adapter's classification is tested:
stream-json for Claude);command at a non-existent path;timeout_seconds (use a small timeout in the test);cwd, then fail with an infra class (for the §7.4 partial-change + fallback path, used from phase 4).fake_agent.py that reads the desired scenario (and any canned stdout/exit code) from an environment variable or an argument the test sets, then writes the canned stdout/stderr, optionally touches a file or sleeps, and exits with the chosen code. Keep it deterministic — no real time/random; bound any sleep.[command, "exec"|"-p", ...], so command must be a runnable executable named codex/claude:
codex.cmd / claude.cmd containing @python "%~dp0fake_agent.py" %*.codex / claude with a #!/usr/bin/env python3 shebang (or a sh wrapper) and set the executable bit. Generate the right launcher for the current OS in a fixture; place it in a tmp_path dir and pass that path as the provider's command (or prepend the dir to PATH).tests/conftest.py, tests/fakes/). A fixture builds the launcher+stub for a requested scenario and returns the command path. Parametrize by provider (codex, claude) so the same scenario matrix runs against both adapters and proves interchangeability.RunStatus/ErrorClass, writes the §10 artifacts (request/stdout/stderr/events/result), and — from phase 4 — that the router falls back only on infra classes and surfaces quality failures without a switch.stream-json).ErrorClass/artifacts./run-checks green.