write-xbrief SKILL.md skillA
write-xbrief from eltmon/overdeck is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eltmon/overdeck/write-xbrief@git:20260924.f5d6c8ePins git:20260924.f5d6c8e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eltmon/overdeck
- Path
sync-sources/skills/write-xbrief/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260924.f5d6c8e, committed Sep 24, 2026
- First version recorded
- Aug 2, 2026
- Size
- 11,600 bytes
- Repository stars
- 35
- License
- MIT
Write an xBRIEF spec and continue.json directly — without launching the interactive planning agent. The workspace copy lives in the runtime dir `.overdeck/`; finalize reads it and promotes the canonical spec to `.pan/specs/` in the project repo. Use when the work is well-understood and the agent can author the plan from the issue body and codebase alone. Also use when you ARE the work agent and need to self-plan before implementing. Covers the full xBRIEF v0.8 schema, continue.json format…
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
# Write xBRIEF — Direct Plan Authoring Use this skill when you want to author an xBRIEF plan directly, bypassing the interactive planning agent. This is appropriate when: - The work is well-scoped and doesn't need a Q&A discovery session - You are a work agent that received an issue without a pre-existing plan - The issue is small enough that a full planning session would cost more than the work itself - You need to rewrite or patch a broken xBRIEF before continuing work After writing the plan, run `pan plan finalize` to materialize xBRIEF tasks and promote the spec to `.pan/specs/` in the project repo (or the configured plan-home repo for polyrepo projects). --- ## Step 1 — Explore First Before writing a single line of JSON, read the issue and explore the relevant code. A plan written without codebase context will have wrong file paths, wrong difficulty estimates, and spurious edges. Minimum exploration: - Read the issue body and the canonical PRD at `.pan/drafts/<issue-id-lowercase>.md` in the project repo - Grep for the primary symbols, commands, or files the issue mentions - Identify which subsystems are affected and how many files will change …
Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/write-xbrief@sha256:7e73c15a8dfec3c4The line at the top of this page pins the label git:20260924.f5d6c8e, 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_7rx33a7unydiypuj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 2, 2026 and Sep 24, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.f5d6c8e latest | 2026-09-24 | f5d6c8e | 11,600 B | A | view · diff |
| git:20260919.a068d61 | 2026-09-19 | a068d61 | 11,603 B | A | view · diff |
| git:20260918.7b95344 | 2026-09-18 | 7b95344 | 10,587 B | A | view · diff |
| git:20260917.83580e3 | 2026-09-17 | 83580e3 | 12,712 B | A | view · diff |
| git:20260802.b0e7dd4 | 2026-08-02 | b0e7dd4 | 12,682 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 (11600 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
eltmon/overdeck · 35 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7rx33a7unydiypuj GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/write-xbrief GET https://markdownregistry.com/api/v1/blob/7e73c15a8dfec3c48f2cb1055bb321e90e378c12dc251d1087f3d05a6e4cedfa
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.