bmad-module-ultracode-goal-stack from armelhbobdad/bmad-module-ultracode-goal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
Stack skill for bmad-module-ultracode-goal — 7 libraries with 9 integration patterns, composed from tag-pinned skills for BMAD Method v6.12.0 (the installer and BMM skills), BMad Builder v2.2.2, TEA v1.27.2, graphify v0.9.92 and IWE 0.28.0, plus the docs-only Claude Code skill (pin v2.1.283, recorded for reference). Use when reasoning about how the installer discovers, configures and registers BMM, BMad Builder and TEA, where TEA's ATDD sits in the BMM story cycle, how deprecated v6 IDs flow…
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
# bmad-module-ultracode-goal Stack Skill
> 7 libraries | 9 integration patterns | Forge tier: Deep | compose-mode (no architecture document; every integration comes from a contract documented in a constituent skill)
## Integration Patterns
### Cross-Cutting Patterns
#### Module registration through `module.yaml` + `module-help.csv` (installer, BMM, BMad Builder, TEA)
The installer defines the registration contract, and the three modules ship to it:
- [from skill: bmad-method-installer] A module ships a `module.yaml` the installer can find. Its `code` becomes the module id, the `_bmad/<code>` folder and the `[modules.<code>]` TOML table. Keys with `prompt` become install questions (`scope: user` → `config.user.toml`, otherwise `config.toml`). `module-help.csv` sits at the module root with the 13 canonical columns and is merged into `_bmad/_config/bmad-help.csv` by `mergeModuleHelpCatalogs()`. Every skill is a folder whose `SKILL.md` frontmatter `name` equals the folder name (Adoption Steps 1–5); the pinned v6.12.0 `parseSkillMd()` also skips a skill without a non-empty string `description`.
…
The line at the top of this page pins the label git:20261019.5e70e60, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_j3lbienfk3grbeeo
GET https://markdownregistry.com/api/v1/resolve?ref=armelhbobdad/bmad-module-ultracode-goal/bmad-module-ultracode-goal-stack
GET https://markdownregistry.com/api/v1/blob/9da8c23b8b438dff09a45d9fd1b152885bc8e4f365f5f945a1d00616522418e8
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.
armelhbobdad/bmad-module-ultracode-goal · skf-skills/bmad-builder/2.2.2/bmad-builder/SKILL.md · Describes the BMad Builder v2.2.2 module (code bmb): the skills it registers under skills/ — bmad-agent-builder…
armelhbobdad/bmad-module-ultracode-goal · skf-skills/bmad-method-installer/6.12.0/bmad-method-installer/SKILL.md · Module discovery and registration internals of the bmad-method v6.12.0 installer (npx bmad-method install): where it…
armelhbobdad/bmad-module-ultracode-goal · skf-skills/cc-primitives/2.1.283/cc-primitives/SKILL.md · Claude Code v2.1.283 primitives that UltraCode Goal composes, from the official docs: /goal, Auto Mode and permission…
armelhbobdad/bmad-module-ultracode-goal · skf-skills/cc-primitives/2.1.306/cc-primitives/SKILL.md · Claude Code v2.1.306 primitives that UltraCode Goal composes, from the official docs: /goal, Auto Mode, permission…
