engine-design
Describe what you want to build, in plain words — I'll help you write it down clearly, check it holds together, and settle it as the description to build from.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 0
- Forks
- 3
01 前言 Front Matter
- name
- engine-design
- description
- Describe what you want to build, in plain words — I'll help you write it down clearly, check it holds together, and settle it as the description to build from.
02 资源文件 1
- 参考文档agents/openai.yaml223 B
03 SKILL.md 正文
<!-- GENERATED by .engine/tools/codex_gen.py from .claude/skills/engine-design/SKILL.md — edit that source and regenerate; never edit this file by hand. -->
Steps
- Read the runbook
.engine/operations/product-intake.mdand follow it with the operator, one step at a time: lay out the pieces of what they want and confirm the shape together, agree on how much detail to capture now, then ask them to type$engine-start— the write-up underdocs/spec/, its checks and the operator's go-ahead all happen in Build, and reach the project through the pull request they merge. Keep the procedure in the runbook — this command is just the way the operator starts it.
Notes
This is a command the operator types to describe what they want built — it is never started on the engine's
own initiative. Everything it produces is plain, readable files inside the operator's own project, written in
Build and landing through a pull request; while exploring, the engine proposes and nothing is written. Nothing
is treated as settled until they say so, and a settled description can always be changed later — the engine
just asks the operator to confirm the change on the pull request first (by applying the guardrail-ack label),
so it is never a quiet edit. If the project's GitHub connection isn't reachable, Build cannot open, so the intake
proposes and waits and says so — what the operator said is kept in the conversation. Once a description is
settled, the same command can turn it into a build order and a list of things to build — the work a build picks
up from.
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.