System prompts¶
6 verified entries in plugin / system.
atomic-landing¶
plugin:system:atomic-landing
A config plugin — the trunk checkout is the fleet's one landing door, so a merge must be trivial by the time it reaches it: sync and resolve in YOUR OWN worktree, land only when your branch already contains the trunk, and wait rather than race for a busy door.
| Field | Value |
|---|---|
| Source path | .spec/spexcode/.plugins/prompts/atomic-landing/spec.md |
| Source revision | 1b8b7876e9afa9bebffc9b80d149c4004704490e |
| Content SHA-256 | 20db40836c79e9715ff18419cc65991b541ad2e108be0e96360ce1588cbf0439 |
| Content role | prompt |
## Landing is atomic
1. In your worktree, merge `<base>` into the branch, resolve conflicts there, and rerun the proof.
2. Immediately before landing, require `git merge-base --is-ancestor <base> <branch>`; otherwise sync again.
3. A clean textual merge is not product proof; the synced branch's verification is required.
`spex guide spec` has the shared-checkout mid-merge rule.comment-altitude¶
plugin:system:comment-altitude
A config plugin — code comments navigate non-obvious local reasoning; specs own product intent and contract.
| Field | Value |
|---|---|
| Source path | .spec/spexcode/.plugins/core/comment-altitude/spec.md |
| Source revision | 1b8b7876e9afa9bebffc9b80d149c4004704490e |
| Content SHA-256 | 730c420545f7c1ce2717fb11efeb4038188993f875cae56a96ed4df81ffc94ee |
| Content role | prompt |
Specs own intent, invariants, policy, and observable contracts. Comments only navigate non-obvious local decisions.
`spex guide spec` has the comment-altitude details.core¶
plugin:system:core
A config plugin — the minimal spec-discipline contract folded into every launched agent.
| Field | Value |
|---|---|
| Source path | .spec/spexcode/.plugins/core/spec.md |
| Source revision | 7a0549d54f9f1ed8d0f927c93a76e6dd8bbd53c2 |
| Content SHA-256 | 762a0ec69185dc7b544ecac8b176896667ef8bfe16cf4c74f5c0a1ddb41965bc |
| Content role | prompt |
Use noun-first CLI commands; `spex help` is the authoritative command map.
Anything a human needs to inspect, whether a file or a local webpage, goes out through `spex session files add` or
`spex session web add`: never paste an absolute path or `host:port`, and never start a static server yourself.
When this session has a clearly running child session (`active` or `parked`), the parent is supervising rather
than finished: declare `park`, not `done`/`awaiting`, until the child reports a settled state.
1. **Spec first:** before governed code, read its spec body with `spex spec owner <path>` or `spex spec search`.
Update that current-state body with any changed intent.
2. **Commit before declare:** commit the code and spec it justifies before done or merge; independent intent gets
its own node.
3. **Keep the loss signal honest:** run `spex spec lint` (the blocking correctness gate) and `spex eval lint --changed`. Measure changed scenarios
through the real product, commit the verified tree, then file with `spex eval add`; the reading's `codeSha` must name that commit.forge-link¶
plugin:system:forge-link
A config plugin — agents link an issue or change request opened through the resolved forge to the spec node it serves via one Spec: <id> body line.
| Field | Value |
|---|---|
| Source path | .spec/spexcode/.plugins/prompts/forge-link/spec.md |
| Source revision | 6ad4aa204a7aec2ec1d722119759042685c20849 |
| Content SHA-256 | 38165e62b25640cf7364dc1099fbb594efc3986829eab9f674721a2f9cd3feef |
| Content role | prompt |
Every forge issue or change request body includes `Spec: <node-id>` (comma-separate several). Use each node's
leaf directory name, not its slash path; `spex graph --json` lists valid ids.memory-hygiene¶
plugin:system:memory-hygiene
A config plugin — keep the project-keyed agent memory free of session- and role-specific facts, so N agents in one folder never inherit a confused identity.
| Field | Value |
|---|---|
| Source path | .spec/spexcode/.plugins/prompts/memory-hygiene/spec.md |
| Source revision | 6ad4aa204a7aec2ec1d722119759042685c20849 |
| Content SHA-256 | db47d19b65cd19eaab3e873dd7689853cc14cc784ed4fddb7ff041e70931ab8a |
| Content role | prompt |
## Memory hygiene
Project memory is shared by the main checkout and all worktrees. Store only durable cross-session project/user
facts. Never store this task, transient worktree state, a one-off decision, role, or identity. On a non-main
`node/<id>` worktree, record no memory at all; land a durable lesson first, then record it from main.reproduce-before-fix¶
plugin:system:reproduce-before-fix
A config plugin — a bug fix must first REPRODUCE the failure as a failing eval, then fix, verify, commit, and file the passing eval. The fail→pass pair on one scenario is the fix's proof (the A/B).
| Field | Value |
|---|---|
| Source path | .spec/spexcode/.plugins/prompts/reproduce-before-fix/spec.md |
| Source revision | 1b8b7876e9afa9bebffc9b80d149c4004704490e |
| Content SHA-256 | 56b185188979cdc88e39fc69f4001acb224eb9fd8f7fc1b04c7604e3c5eb46dc |
| Content role | prompt |
## Reproduce before you fix
For a bug fix, the fail→pass pair on one scenario is the repair proof. New intent has no prior failure to
reproduce; `spex guide eval` has the A/B filing sequence.