← ClaudeAtlas

dayz-feature-speclisted

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. Use for "spec de la feature", "definición de done", "criterios de aceptación", "antes de implementar", acceptance criteria, consistency/analyze gate, spec checklist or "¿está listo para codear?". Run after planning and before dayz-mod-workflow; compose with rigorous-data-audit for data-critical work.
willy92wins/DayZ-Modding-Knowledge-Pack · ★ 25 · AI & Automation · score 78
Install: claude install-skill willy92wins/DayZ-Modding-Knowledge-Pack
# 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). Skip for: 1-line typos, trivial reversible tweaks (default keybind, stringtable key, path slash). R3's small-reversible-changes-go-direct rule wins — a spec here would be ceremony. ## The flow ``` Plan mode ─► dayz-feature-spec ─► [code] ─► dayz-feature-spec ─► dayz-mod-workflow ─► R5 batched Step 1 spec + Step 2 checklist (GATE) Step 3 analyze