菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Write a tracer-bullet card — a precise specification for one thin end-to-end slice of work. Use when scoping a new slice, defining what to build next, or breaking a feature into provable increments. Covers target behavior, boundary crossings, risks, and definition of done.
Create characterization tests (Golden Master) for existing code so you can refactor or replace safely. Use before refactoring, strangler-replacing, or modifying code with unclear behavior. Captures observable behavior with a minimal harness, producing tests, fixtures, and a coverage report.
Methodology triage consultant for tracer-bullet development. Use when unsure which pragma skill to run next, when starting a new project, or when the current approach feels stuck. Interviews the user, assesses state, and recommends the next pragma skill.
| 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)