Skip to main content

bmad-module-builder

Plans, creates, and validates BMad modules. Use when the user requests to 'ideate module', 'plan a module', 'create module', 'build a module', or 'validate module'.

소스 정보

저장소
bmad-code-org/bmad-builder
최근 소스 활동
2026년 8월 29일 16:36
감지된 SKILL.md 언어
영어
스타
209
포크
54

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
20 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
bmad-module-builder
description
Plans, creates, and validates BMad modules. Use when the user requests to 'ideate module', 'plan a module', 'create module', 'build a module', or 'validate module'.
# BMad Module Builder ## Overview This skill helps you bring BMad modules to life — from the first spark of an idea to a fully scaffolded, installable module. It offers three paths: - **Ideate Module (IM)** — A creative brainstorming session that helps you imagine what your module could be, decide on the right architecture (agent vs. workflow vs. both), and produce a detailed plan document. The plan then guides you through building each piece with the Agent Builder and Workflow Builder. - **Create Module (CM)** — Takes an existing folder of built skills (or a single skill) and scaffolds the module infrastructure that makes it installable. For multi-skill modules, generates a dedicated `-setup` skill. For single skills, embeds self-registration directly into the skill. Supports `--headless` / `-H`. - **Validate Module (VM)** — Checks that a module's structure is complete and correct — every skill has its capabilities registered, entries are accurate and well-crafted, and structural integrity is sound. Handles both multi-skill and standalone modules. Supports `--headless` / `-H`. **Args:** Accepts `--headless` / `-H` for CM and VM paths, an initial description for IM, or a path to a skills folder or single SKILL.md file for CM/VM. ## On Activation Load available config from `{project-root}/_bmad/config.yaml` and `{project-root}/_bmad/config.user.yaml` (root level and `bmb` section). If neither exists, fall back to `{project-root}/_bmad/bmb/config.yaml` (legacy per-module format). If still missing, let the user know `bmad-builder-setup` can configure the module at any time. Use sensible defaults for anything not configured. Detect user's intent: - **Ideate / Plan** keywords or no path argument → Load `./references/ideate-module.md` - **Create / Scaffold** keywords, a folder path, or a path to a single SKILL.md file → Load `./references/create-module.md` - **Validate / Check** keywords → Load `./references/validate-module.md` - **Unclear** → Present options: - **Ideate Module (IM)** — "I have an idea for a module and want to brainstorm and plan it" - **Create Module (CM)** — "I've already built my skills and want to package them as a module" - **Validate Module (VM)** — "I want to check that my module's setup skill is complete and correct" If `--headless` or `-H` is passed, route to CM with headless mode.
GitHub에서 보기