dayz-feature-spec SKILL.md skillA
dayz-feature-spec from willy92wins/dayz-modding-knowledge-pack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add willy92wins/dayz-modding-knowledge-pack/dayz-feature-spec@git:20261001.e42d2f4Pins git:20261001.e42d2f4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- willy92wins/dayz-modding-knowledge-pack
- Path
skills/dayz-feature-spec/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.e42d2f4, committed Oct 1, 2026
- First version recorded
- Aug 24, 2026
- Size
- 13,418 bytes
- Repository stars
- 17
- License
- MIT
Define and quality-gate a non-trivial DayZ feature before implementation. Produces measurable Success Criteria, Given/When/Then scenarios with in-game repro, resolved ASSUMED markers, and a Forward Contract for every classname, model.cfg selection, .p3d proxy, stringtable/layout key or injected object the next phase consumes. Then runs a spec checklist and a read-only spec↔plan↔tasks/HANDOFF↔code consistency gate for coverage gaps, contradictions, terminology drift and unverified references.…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# DayZ Feature Spec The DayZ-adapted spine of spec-driven development: define *what done means* and *how it will be verified* before touching code, then gate the artifacts for consistency before spending an in-game test cycle. This is the local adaptation of GitHub's [spec-kit](https://github.com/github/spec-kit) `specify → clarify → analyze → implement` flow. The generic app scaffolding (TDD red-green, contract tests, user-story-as-independent-MVP slicing, the `specify` CLI, GitHub-issue export, extension marketplace) is intentionally dropped — see "What this drops" below. What is kept is the discipline that already maps to R7/R8/R8-extended and G1–G3, plus one thing they lack: an explicit **artifact-level** consistency gate. ## When to use / when to skip Use before implementing: - a new mod feature, or any change touching >1 file (aligns with R3), - anything data-critical (persistence, progression) — then also invoke `rigorous-data-audit`, - anything where "done" is not self-evident, or where a later phase/consumer reads this phase's output (R8-extended forward contract). …
Read the whole file at its exact version.
How to install
mdr add willy92wins/dayz-modding-knowledge-pack/dayz-feature-spec@sha256:97a37cf2e0fd4ddfThe line at the top of this page pins the label git:20261001.e42d2f4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hydq3vvfzq35sh6i)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 24, 2026 and Oct 1, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.e42d2f4 latest | 2026-10-01 | e42d2f4 | 13,418 B | A | view · diff |
| git:20260924.fa4f23e | 2026-09-24 | fa4f23e | 13,526 B | A | view · diff |
| git:20260831.ef754a8 | 2026-08-31 | ef754a8 | 12,854 B | A | view · diff |
| git:20260830.148a55d | 2026-08-30 | 148a55d | 11,876 B | A | view · diff |
| git:20260824.4da9bc3 | 2026-08-24 | 4da9bc3 | 11,698 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 (13418 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
willy92wins/dayz-modding-knowledge-pack · 17 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hydq3vvfzq35sh6i GET https://markdownregistry.com/api/v1/resolve?ref=willy92wins/dayz-modding-knowledge-pack/dayz-feature-spec GET https://markdownregistry.com/api/v1/blob/97a37cf2e0fd4ddf483ee25e361979624e8c0c7ac713bc4169ecf44cb21ed001
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.