ucg-formalize SKILL.md skillA
ucg-formalize from armelhbobdad/bmad-module-ultracode-goal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add armelhbobdad/bmad-module-ultracode-goal/ucg-formalize@git:20261105.2f82493Pins git:20261105.2f82493 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- armelhbobdad/bmad-module-ultracode-goal
- Path
skills/ucg-formalize/SKILL.md- Versions recorded
- 15
- Latest version
- git:20261105.2f82493, committed Nov 5, 2026
- First version recorded
- Aug 2, 2026
- Size
- 26,679 bytes
- Repository stars
- 5
- License
- a license file GitHub does not identify
Opt-in standalone readiness verdict for one BMAD Epic via the `/ucg-formalize <epic>` trigger. Runs the formalize_check.py kernel, auto-remediates machine-derivable gaps, delegates judgment to one throwaway subagent, and emits the canonical five-key headless envelope. Use when an operator asks to "formalize an epic", "check epic readiness", or runs `/ucg-formalize`.
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
# UCG Formalize
## Overview
`/ucg-formalize <epic>` is the **opt-in, operator-on-demand** readiness verdict for a
single BMAD Epic — the thin LLM layer over the readiness kernel
(`scripts/formalize_check.py`). It adapts the kernel's graduated verdict
(ready / remediable / blocked) into the canonical five-key headless envelope; it never
recomputes the readiness verdict. Each verdict and remediation lands in
`.decision-log.md`.
## Conventions
- This skill ships no `scripts/` or `customize.toml` of its own: the kernel
(`formalize_check.py`, `headless_envelope.py`), `customize.toml`, and `references/`
all live in the **parent `ultracode-goal` module**. `{ucg-root}` names that module
directory — `{project-root}/_bmad/ucg/ultracode-goal` in an installed project, or
`{project-root}/skills/ultracode-goal` in a source checkout of the module itself.
Resolve it once (first of those two that exists) and qualify every script path with
it, so `{ucg-root}/scripts/…` and `{ucg-root}/customize.toml` resolve from any cwd.
It is deliberately **not** `{skill-root}`: this is a top-level skill, so `{skill-root}`
…Read the whole file at its exact version.
How to install
mdr add armelhbobdad/bmad-module-ultracode-goal/ucg-formalize@sha256:51b234526cca4649The line at the top of this page pins the label git:20261105.2f82493, 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_f57ruklirvfaze3w)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 15 versions of this file, between Aug 2, 2026 and Nov 5, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.2f82493 latest | 2026-11-05 | 2f82493 | 26,679 B | A | view · diff |
| git:20261105.a3e3cbf | 2026-11-05 | a3e3cbf | 26,675 B | A | view · diff |
| git:20261105.6dc142e | 2026-11-05 | 6dc142e | 25,691 B | A | view · diff |
| git:20261103.325b9af | 2026-11-03 | 325b9af | 25,661 B | A | view · diff |
| git:20261103.f66e826 | 2026-11-03 | f66e826 | 25,588 B | A | view · diff |
| git:20261024.7340211 | 2026-10-24 | 7340211 | 25,182 B | A | view · diff |
| git:20261024.9b051c0 | 2026-10-24 | 9b051c0 | 25,019 B | A | view · diff |
| git:20261018.201e120 | 2026-10-18 | 201e120 | 25,007 B | A | view · diff |
| git:20261018.fa6de02 | 2026-10-18 | fa6de02 | 25,086 B | A | view · diff |
| git:20261017.518f9f2 | 2026-10-17 | 518f9f2 | 24,354 B | A | view · diff |
| git:20261017.c1f322e | 2026-10-17 | c1f322e | 23,449 B | A | view · diff |
| git:20261017.22f6ac0 | 2026-10-17 | 22f6ac0 | 20,629 B | A | view · diff |
| git:20260928.6982d7b | 2026-09-28 | 6982d7b | 19,754 B | A | view · diff |
| git:20260806.976553e | 2026-08-06 | 976553e | 19,160 B | A | view · diff |
| git:20260802.c6f161d | 2026-08-02 | c6f161d | 11,839 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 (26679 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
armelhbobdad/bmad-module-ultracode-goal · 5 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_f57ruklirvfaze3w GET https://markdownregistry.com/api/v1/resolve?ref=armelhbobdad/bmad-module-ultracode-goal/ucg-formalize GET https://markdownregistry.com/api/v1/blob/51b234526cca4649b526e0ca4ed7d792087a2bfb17e20c382add12b2cec99d50
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.