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/bmad-method-installer.md

View on GitHub
# bmad-method-installer (constituent)

- **Version:** 6.12.0 (BMAD-METHOD tag `v6.12.0`, commit `05bfbd46`)
- **Export count:** 118 (source skill metadata)
- **Confidence:** T1 (source skill: Deep, reference-app)
- **Source skill:** `skf-skills/bmad-method-installer/6.12.0/bmad-method-installer`

## Key exports used in this stack

| Export | Role | Anchor (from source skill provenance) |
|--------|------|----------------------------------------|
| `Installer.install()` | Phase order of an install/update | `tools/installer/core/installer.js` |
| `Installer.quickUpdate()` | Update installed modules, prompt only for new keys | `tools/installer/core/installer.js` |
| `OfficialModules.findModuleSource()` | Source lookup order core → bmm → external → custom | `tools/installer/modules/official-modules.js` |
| `generateModuleConfigs()` | Per-module `config.yaml` with core keys spread in | `tools/installer/core/installer.js` |
| `mergeModuleHelpCatalogs()` | `module-help.csv` → `_bmad/_config/bmad-help.csv` | `tools/installer/core/installer.js` |
| `resolveInstalledModuleYaml()` | Locating an installed module's `module.yaml` (no network) | `tools/installer/project-root.js` |
| `loadRemovalLists()` | `removals.txt` and stale-skill cleanup | `tools/installer/ide/_config-driven.js` |

## Usage patterns (from source skill)

- `npx bmad-method install --yes --directory <project> --modules bmm --tools claude-code` — `--tools` is required for a fresh `--yes` install.
- A module is found via `module.yaml`; its `code` names `_bmad/<code>` and `[modules.<code>]`; prompt keys (`scope: user` → `config.user.toml`) become config; `module-help.csv` (13 columns) is merged into `bmad-help.csv`; skills whose `SKILL.md` `name` equals the folder are copied into `.claude/skills`.
- Modules installed by their own CLI into `_bmad/<code>` are kept as preserved modules when no source resolves.
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: 472kUpdated 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