war-machine SKILL.md skillA
war-machine from ljferrer/workauditrefine is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ljferrer/workauditrefine/war-machine@git:20261030.0645294Pins git:20261030.0645294 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ljferrer/workauditrefine
- Path
skills/war-machine/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261030.0645294, committed Oct 30, 2026
- First version recorded
- Sep 12, 2026
- Size
- 12,462 bytes
- Repository stars
- 11
- License
- MIT
Convert design specs into merged implementation plans plus a campaign roadmap — the middle step of the WAR pipeline (survey → machine → campaign → aftermath). Consumes the freshest survey manifest (or explicit spec paths), runs a drafter + adversarial-grill agent pair per spec strictly serially, writes plans to docs/plans/ and a roadmap to docs/roadmaps/, stamps the manifest consumed, and prints the /war-campaign handoff — it never launches the campaign and never red-teams. Use when the user…
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
# /war-machine — specs → plans + roadmap
You convert war-shaped design specs (the input shape) into merged implementation plans, then bind
them into a campaign roadmap. You rely on `/war-strategy` for the merged plan + roadmap templates
and its with-artifact conversion doctrine ("Given a SPEC (the input shape): author the merged plan
into `docs/plans/` yourself") — consume [`skills/war-strategy/SKILL.md`](../war-strategy/SKILL.md)
§2 and §3 by reference, **never fork the templates**. You stop at plans + roadmap: `/war-campaign`
is a ~12+ hour human-launched commitment and is never auto-invoked.
**Merged-output directive.** Conversion emits the merged shape — one plan whose Part 1 is the
decision digest distilled from the source spec (citing the spec path; issue-derived claims keep
the `(verified: issue #N (<date>))` source form, D11) and whose Part 2 is the decomposed phases,
per the `/war-strategy` §2 merged plan template. The spec's assumption rows — its
`## Assumptions ledger` where it has one, otherwise its `[assumed: … — if wrong: …]` design-tree
entries and open-risk notes — are never dropped silently: each is carried forward
…Read the whole file at its exact version.
How to install
mdr add ljferrer/workauditrefine/war-machine@sha256:23fa58f779598b82The line at the top of this page pins the label git:20261030.0645294, 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_zuboxqzebkabggak)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 12, 2026 and Oct 30, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.0645294 latest | 2026-10-30 | 0645294 | 12,462 B | A | view · diff |
| git:20261030.b0f6bab | 2026-10-30 | b0f6bab | 12,412 B | A | view · diff |
| git:20261030.e0512aa | 2026-10-30 | e0512aa | 12,412 B | A | view · diff |
| git:20261027.d88b6d3 | 2026-10-27 | d88b6d3 | 11,760 B | A | view · diff |
| git:20260912.322a7db | 2026-09-12 | 322a7db | 11,449 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 (12462 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
ljferrer/workauditrefine · 11 stars · license MIT · pushed 2026-11-04 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_zuboxqzebkabggak GET https://markdownregistry.com/api/v1/resolve?ref=ljferrer/workauditrefine/war-machine GET https://markdownregistry.com/api/v1/blob/23fa58f779598b824b5a6af139aeac3bde793a718c19b2c29875e6eef9ffdac5
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.