prime-context skillA
prime-context is agent-read markdown (skill) from swingerman/engineer: Use before starting pipeline work on a Ready feature the agent hasn't worked yet. Triggers — "/engineer.prime-context", "prime context", "load context before we start", "get up to speed on feature X"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# prime-context
Load working memory before pipeline work on a Ready feature — the convergent counterpart to `discuss`. Forked from `superpowers:brainstorming` but inverted: no exploration, just loading and orienting. Produces no artifact.
## When to use
A prep step (not a checkpoint) between `feature-init` and `discover-acs`, on any feature the agent hasn't already worked this session.
**Skip when:** the agent just created the feature this session (context already warm). **Not for:** exploring whether a feature is worth doing (`discuss`).
## Workflow
1. **Resolve + locate** — resolve the methodology root + manifest via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py` (see `references/resolving.md`); locate the feature (slug arg or branch name). Reject if no folder / no `feature.md`. **Layout disambiguation:** if the project has BOTH a `features/NNN-*/` and a `specs/NNN-*/` tree (a speckit migration in progress), state which holds this feature's artifacts; and if more than one acceptance-IR convention is present (`features/NNN/.build/spec.json` vs an `acceptance-pipeline/ir/` per-GWT layout), name the one this feature uses — so the load doesn't rediscover the split ad-hoc…
…Read the whole file at its exact version.
How to install
mdr add swingerman/engineer/prime-context@git:20260710.5dd248amdr add swingerman/engineer/prime-context@sha256:6ea19461d5817775Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_xfj4vsomhg7gzl6z)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260710.5dd248a latest | 2026-07-10 | 5dd248a | 3,488 B | A | view · diff |
| git:20260619.d0fa8c9 | 2026-06-19 | d0fa8c9 | 3,053 B | A | view · diff |
| git:20260604.e249d7b | 2026-06-04 | e249d7b | 2,717 B | A | view · diff |
| git:20260516.48406db | 2026-05-16 | 48406db | 2,140 B | A | view · diff |
| git:20260515.595977f | 2026-05-15 | 595977f | 2,075 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3488 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
swingerman/engineer · 150 stars · license MIT · pushed 2026-09-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_xfj4vsomhg7gzl6z GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/prime-context GET https://markdownregistry.com/api/v1/blob/6ea19461d58177752eaa957569887da28c5f95230601babcc7624847986f82a1
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.