event-modeling-implement
/event-modeling-implement
Use when building a single ratified event-modeling slice (status: ready-to-implement) into merged, tested code — the one phase where the agent builds rather than facilitates. Gates on readiness, treats the slice doc as the read-only spec, surfaces gaps instead of deciding them silently, and requires tests traceable to the doc's invariants and scenarios.
- Author
- milehimikey ↗
- Repository
- em ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when building a single ratified event-modeling slice (status: ready-to-implement) into merged, tested code — the one phase where the agent builds rather than facilitates. Gates on readiness, treats the slice doc as the read-only spec, surfaces gaps instead of deciding them silently, and requires tests traceable to the doc's invariants and scenarios.
Original author description
Use when building a single ratified event-modeling slice (status: ready-to-implement) into merged, tested code — the one phase where the agent builds rather than facilitates. Gates on readiness, treats the slice doc as the read-only spec, surfaces gaps instead of deciding them silently, and requires tests traceable to the doc's invariants and scenarios.
How it works
SKILL.md has no level-two headings · 52 lines, 545 words
SKILL.md preview
---
name: event-modeling-implement
em-version: 1.19.5
description: >-
Use when building a single ratified event-modeling slice (status: ready-to-implement) into
merged, tested code — the one phase where the agent builds rather than facilitates. Gates on
readiness, treats the slice doc as the read-only spec, surfaces gaps instead of deciding them
silently, and requires tests traceable to the doc's invariants and scenarios.
---
# Event Modeling — implement
Goal: turn a single `ready-to-implement` slice into merged, verified code — the one phase where
the agent builds rather than facilitates.
**Read `reference/implement.md` before doing any implement work and follow it as the
contract.** In short: gate on `em validate <model>.em --slice-ready <key>` (stop and hand
back if it fails — never edit the doc to make the gate pass); read the project's implementation
constitution before writing code and stay inside its rules; before a project's first slice PR,
land a one-time foundation PR holding every model event (plus the shared interface shell) so
slices only ever import contracts, never invent or reach into a sibling's; build in dependency
order from `em query upstream`, not timeline order; treat the slice doc as
the spec (read-only, except the merge-time `status`/`implementedIn` flip); implement exactly one
slice doc per PR — a `covers:` doc's two keys ship together in that one PR, and an `again` view
instance is a continuation of its originating slice (no doc, status, or PR of its own — it
ships in the originating doc's PR); ship the endpoint a
`ui`-triggered command or `ui`-consumed view obligates, and surface — never invent — one the
model doesn't show; surface every gap to the user instead of deciding it silently; cover every
`INV-<MNEMONIC>-n` and every scenario with tests, proving the citations before merge with
`em coverage <model>.em --slice <key> --tests <dir> --strict` (the default form skips a
`ready-to-implement` slice); in spec-kit projects, allocate via
em-sdd-bridge (redirect mode) and never run `/speckit.specify`.
**Gate: no constitution, no first slice.** The constitution is the project's ratified house rules
— stack and architectural shape (including which implementation skill each slice pattern routes
to), code style, testing norms, NFR baselines, review/merge norms. It lives at
`.specify/memory/constitution.md` in a spec-kit project (when that file exists), otherwise
`constitution.md` beside the model; `em status` reports which, and whether it's there. If it's missing — or its `ratifiedBy:`
is empty, meaning nobody has signed it off — run `reference/implement.md` §7 ("Before the first
slice: the constitution") first: ask its questions conversationally, write the answers in, and
have a human ratify them. Don't decide the project's stack or style yourself to get moving.
That contract applies to any implementing agent, whether or not the session started from
`/event-modeling` — `em contract` prints it to stdout with no `.claude/` awareness required, for
an agent that can run a shell but isn't Claude Code.
If the project ships pattern-specific implementation skills (for example an Axon/DCB skill set
keyed on a slice doc's `pattern:` frontmatter), route by the slice's pattern and follow those —
`reference/implement.md` §2 explains where that hand-off happens, and the constitution's
routing table (§7) is what names the skill set for each pattern.
Preconditions (tool check, model location) are the same as every other phase — see
`../event-modeling-shared/reference/operating-principles.md` — but this phase additionally
requires the target slice to already be ratified; if it isn't, stop and say so rather than
starting on unratified work.
End of phase: PR merged, slice doc flipped to `status: implemented` with `implementedIn`
filled, `em slice index <model-name>.em` run to refresh `README.md`'s Slices table. Implement
doesn't chain to another phase — run it once per ratified slice; `event-modeling-conform`'s
`conform` phase later checks the result against the model.
Files in this package (2)
- SKILL.md 4 KB
- reference/implement.md 35 KB
Versions
The database has no other skills named event-modeling-implement.
Database snapshot: 13.11.2026 · package version d2d3503df53f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100event-modeling
Use when the user runs `/event-modeling` (with or without a phase name), or wants to resume an event-modeling session without specifying which part of the process applies. Reads the model's `.event-modeling.md` state (or the given phase name) and routes to the right focused… - 90event-modeling-engagement
Use when leading an engagement: building a named set of ratified event-modeling slices (`em engagement`) into one independent PR per slice, each against main, by dispatching the em-implementer, em-validator, em-reviewer and em-critic sub-agents, level by level, and handing the… - 90implement-slice
Use when writing code with an AI agent for a slice that already has a spec, or when fixing a bug: test first, smallest change, small commits, one agent per task. - 90build-slice
Build ONE vertical slice of an approved feature design. First agree the code-level implementation choices with the user, then write and get approval for a code-level slice plan (slices/slice-N.md), then build test-first, following the plan exactly, with verification,… - 92implement
Implement a settled plan test-first, one small slice at a time. Read this skill before you write code for a spec or a settled plan. Read it also when the plan is small. Use it when the user says \"implement this\" or \"build it\", or names a spec to implement. - 86slice
Build the next slice of {{Project}} end to end: pick it from docs/STATUS.md, branch, build with tests, run checks, get a security review when the slice is risky, update STATUS and SETUP, open the PR and merge under the owner's rules. Use whenever the owner says "start slice X",…