engine-start
Start building — switch from looking around to making changes, which I'll put up for your approval.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 0
- Forks
- 3
01 前言 Front Matter
- name
- engine-start
- invocation
- operator-typed
- description
- Start building — switch from looking around to making changes, which I'll put up for your approval.
- allowed-tools
- Bash(uv run *)
- disable-model-invocation
- true
03 SKILL.md 正文
Steps
- Switch this session into building by running:
uv run --directory .engine --frozen -- python tools/modes.py set-build --session "${CLAUDE_CODE_SESSION_ID}"(the engine works out this session's identity automatically. If the command reports it could not identify the session, say so plainly: the stance stays as it was, and building has not started.) This step needs no network and no accepted activation — entering Build is the operator's own control, and it must work whether or not memory-write qualification has converged on this machine. - Tell the operator, in plain words, that the session is now building — say: "Building — I'll make changes and submit them as a pull request for your approval."
- Begin the work by following
.engine/operations/build-orchestration.md, the spine that names one runbook per phase: start with.engine/operations/build-kickoff.md— open the draft pull request and bind the sealed plan — and read each later runbook only when the coordinator'sstatusnames it. - Once the Build is authorized, keep moving through its actionable work. A progress report is not a handoff: continue the next planned step unless the Build is submission-ready or a real authority boundary requires the operator's decision. Do not schedule a self-wakeup instead of working.
Notes
This is a command you type to begin building. I won't start building on my own — that is your call: type
/engine-start and the work begins. Approving a plan I've shown you imports it as a draft for the Engine's
planning — it does not start building; the typed command is the only way in, on either runtime.
Memory-write qualification is not part of this command. It converges by itself at session start, and when it
has not, the session simply runs unqualified: memory still reads, and writing waits. If that matters to what
you are about to do, /engine-status says so in plain words.
04 同仓库更多 Skills
templates
暂无简介
engine-bad
A negative fixture skill for engine/check/skill-coherence — operator-typed but not locked.
engine-dangling-route
A negative fixture route whose active target points at an operation that is not there.
engine-overlong-demo-route
This demonstration route deliberately carries a description that runs well past the one-hundred-and-twenty-character ceiling the route budget check enforces, so the guard bites on a real over-length description.
engine-bad
A deliberately broken fixture — an engine Codex command shipped WITHOUT its operator-only policy companion.
engine-widget
A deliberately one-sided fixture — a Claude command with no Codex twin and no ledger entry.