Skip to content

armelhbobdad/bmad-module-ultracode-goal / skf-skills/bmad-module-ultracode-goal-stack/1.0.0/bmad-module-ultracode-goal-stack

bmad-module-ultracode-goal-stack

Verified

Stack skill for bmad-module-ultracode-goal — 3 libraries with 3 integration patterns, composed from version-pinned skills for BMAD Method v6.12.0 (BMM skills and the installer) and BMad Builder v2.2.2. Use when reasoning about how a BMAD module is discovered, configured and registered by the installer next to BMM and BMad Builder, or how deprecated core IDs flow through the v6 shims. NOT for: individual library usage outside this project's conventions.

references/integrations/bmad-method-installer-bmad-builder.md

View on GitHub
# bmad-method-installer + bmad-builder

- **Type:** Configuration Bridge
- **Detection:** constituent-documented-contract (compose-mode; no co-import files)
- **Confidence:** T1-low (constituent-documented-contract) [composed]

BMad Builder (code `bmb`) is an external module. The installer clones external registry modules to `~/.bmad/cache/external-modules` and searches for `module.yaml` at the registry `module_definition` path, then `skills/` and `src/` (one level deep), then the repo root; BMad Builder keeps `skills/module.yaml`. Offline, `resolveInstalledModuleYaml()` also checks `*-setup` skills under `skills/` (BMB `{setup-skill}/assets/module.yaml`). The two `bmb` prompt keys land in `[modules.bmb]` of `_bmad/config.toml`; `skills/module-help.csv` rows are merged into `bmad-help.csv`.

**Convention:** `bmad-bmb-setup` (SB) is BMad Builder's own configure path — it writes `config.yaml` and `config.user.yaml` into `{project-root}/_bmad`.

Evidence: [from skill: bmad-method-installer] Adoption Steps 1–4; `references/pattern-module-discovery.md` (BMB setup-skill layout). [from skill: bmad-builder] Configuration table; Usage Patterns row SB.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall