mission-slice-sop skillA
mission-slice-sop is agent-read markdown (skill) from mvschwarz/openrig: Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC..
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
# Mission/Slice SOP — Part A Use this skill to actually **do** mission/slice work: track on the canonical files, record what you proved, hand off through them, and survive compaction on them. **Do the work described here; do not merely explain the protocol.** **Full convention SSOT:** repo `docs/reference/sdlc-conventions.md`; installed `$OPENRIG_HOME/reference/sdlc-conventions.md`. This skill is the concise Part-A teaching surface and does not replace the full convention. ## Resolve the work first Run `rig whoami --json`, then resolve `project.yaml -> mission.yaml -> active slice.yaml -> selected component or wave map -> addressed context`. The complete lookup and precedence rule is `docs/reference/product-journey-sdlc.md#resolve-the-selected-path` (installed: `$OPENRIG_HOME/reference/product-journey-sdlc.md#resolve-the-selected-path`). Read the selected addresses and source needed for this task; skills available in your profile are capabilities, not a mandatory reading list. No composition means light Part A. Role names and idle seats add no gates. Explicit rigor and authored wave boundaries retain their named checks. …
Read the whole file at its exact version.
How to install
mdr add mvschwarz/openrig/mission-slice-sop@git:20260906.ac21bc2mdr add mvschwarz/openrig/mission-slice-sop@sha256:3c3783d2f2d05ceaPin 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_ptr5jekc64vovqai)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260906.ac21bc2 latest | 2026-09-06 | ac21bc2 | 8,038 B | A | view · diff |
| git:20260830.c08b556 | 2026-08-30 | c08b556 | 7,507 B | A | view · diff |
| git:20260827.622323d | 2026-08-27 | 622323d | 8,041 B | A | view · diff |
| git:20260826.bdc404f | 2026-08-26 | bdc404f | 8,784 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 (8038 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
mvschwarz/openrig · 362 stars · license Apache-2.0 · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ptr5jekc64vovqai GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/mission-slice-sop GET https://markdownregistry.com/api/v1/blob/3c3783d2f2d05cead97c94d10a9af00b397b810a8fdb7d599930fc1ea226305d
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.