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-method-bmm.md

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

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

The installer treats BMM as a built-in module: `findModuleSource()` resolves core → bmm → external → custom; `generateModuleConfigs()` writes BMM's `config.yaml` and the central `config.toml` / `config.user.toml` from `src/bmm-skills/module.yaml` prompts; `mergeModuleHelpCatalogs()` merges `src/bmm-skills/module-help.csv` into `_bmad/_config/bmad-help.csv`; skills in `skill-manifest.csv` are copied into `.claude/skills/<canonicalId>`.

**Convention:** on a fresh v6.12.0 install, BMM's deprecated shims (`bmad-create-story`, `bmad-dev-story`, …) are installed only with `--shims`.

Evidence: [from skill: bmad-method-installer] Pattern Surface rows 5, 12, 13; Key Types (`module-help.csv` columns cite `src/bmm-skills/module-help.csv`); Migration (`--shims`). [from skill: bmad-method-bmm] Pattern Surface rows 2, 19, 20.
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