菜单
Implement one tracer-bullet slice following the inside-out methodology. Use when you have a tracer-bullet card ready to build. Implements functional core first, then imperative shell, then end-to-end wiring, then alignment refactor.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/hashintel/labs --skill slice命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | slice |
| description | Implement one tracer-bullet slice following the inside-out methodology. Use when you have a tracer-bullet card ready to build. Implements functional core first, then imperative shell, then end-to-end wiring, then alignment refactor. |
| argument-hint | [paste tracer-bullet card (or provide path to it)] |
Implement one thin end-to-end slice of functionality, following the inside-out procedure.
The slice is defined by a tracer-bullet card: $ARGUMENTS
Preconditions:
/pragma:capsule first./pragma:card first.Extract from the card: (1) target behavior, (2) boundary crossings, (3) risks/assumptions, (4) definition of done. If the card is incomplete, stop and recommend rerunning /pragma:card.
Follow these steps in order. Do not skip or reorder.
Before writing implementation code:
/pragma:card./pragma:spike first to prototype/observe.Before implementing behavior, translate card Definition of Done into tests:
This is the "create the needle" step: define a narrow path to success first.
Implement using the functional core / imperative shell pattern (Bernhardt):
No frameworks, no infrastructure, no I/O in this step. No speculative abstractions.
Add the minimal I/O boundary connecting the core to the real world. The shell calls the core, never the reverse. No business logic in the shell.
Connect the full path: entry point → shell → core → shell → output. Make it actually run. Write or update an integration test proving the target behavior.
Commit the smallest set of changes that makes the E2E path pass.
Message style: Behavior: <target behavior>
Refactor immediately while context is fresh:
Run the project's existing verification harness. All checks must pass. If any fails, fix and re-run from step 1 of verification.
Separate from the behavior commit. Message style: Refactor: align slice to capsule
Before closing the slice, classify what changed and route updates to the correct authority artifact:
/pragma:capsule update/pragma:roadmap update/pragma:milestone update/pragma:assumptions update/pragma:contractUse explicit none for lanes with no change.
Run /pragma:assumptions update with the slice summary, assumptions made, and validation evidence.
none authority delta must be surfaced
and routed before additional delivery work.none | /pragma:capsule update — [reason]none | /pragma:roadmap update — [reason]none | /pragma:milestone update — [reason]none | /pragma:assumptions update — [reason]none | /pragma:contract — [reason]/pragma:assumptions update (mandatory after every slice)State: delivery, Next: first non-'none' authority delta command (otherwise /pragma:assumptions update), Loop: /pragma:consult (default unless user explicitly continues directly)Read and write a Petri net (SDCPN) document by Automerge URL. Use when creating, editing, or querying Petri nets — adding or removing places, transitions, arcs, color types, differential equations, and parameters.
Create and maintain an Assumption Ledger — a persistent record of assumptions, their confidence, and validation status. Use when starting a new slice, resuming work in a new context window, or when implicit assumptions risk causing drift. Tracks requirements, architecture, and implementation assumptions.
Create or update a concept capsule — the conceptual anchor for a project or feature area. Use before writing code on a new project or feature, or when terms and boundaries feel unclear. Defines glossary, invariants, happy-path scenario, and non-goals.