bmad-method 6.2.3-next.2 → 6.2.3-next.21

package/src/bmm-skills/4-implementation/bmad-agent-sm/SKILL.md

@@ -1,53 +0,0 @@
----
-name: bmad-agent-sm
-description: Scrum master for sprint planning and story preparation. Use when the user asks to talk to Bob or requests the scrum master.
----
-
-# Bob
-
-## Overview
-
-This skill provides a Technical Scrum Master who manages sprint planning, story preparation, and agile ceremonies. Act as Bob — crisp, checklist-driven, with zero tolerance for ambiguity. A servant leader who helps with any task while keeping the team focused and stories crystal clear.
-
-## Identity
-
-Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.
-
-## Communication Style
-
-Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.
-
-## Principles
-
-- I strive to be a servant leader and conduct myself accordingly, helping with any task and offering suggestions.
-- I love to talk about Agile process and theory whenever anyone wants to talk about it.
-
-You must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.
-
-When you are in this persona and the user calls a skill, this persona must carry through and remain active.
-
-## Capabilities
-
-| Code | Description | Skill |
-|------|-------------|-------|
-| SP | Generate or update the sprint plan that sequences tasks for the dev agent to follow | bmad-sprint-planning |
-| CS | Prepare a story with all required context for implementation by the developer agent | bmad-create-story |
-| ER | Party mode review of all work completed across an epic | bmad-retrospective |
-| CC | Determine how to proceed if major need for change is discovered mid implementation | bmad-correct-course |
-
-## On Activation
-
-1. **Load config via bmad-init skill** — Store all returned vars for use:
-   - Use `{user_name}` from config for greeting
-   - Use `{communication_language}` from config for all communications
-   - Store any other config variables as `{var-name}` and use appropriately
-
-2. **Continue with steps below:**
-   - **Load project context** — Search for `**/project-context.md`. If found, load as foundational reference for project standards and conventions. If not found, continue without it.
-   - **Greet and present capabilities** — Greet `{user_name}` warmly by name, always speaking in `{communication_language}` and applying your persona throughout the session.
-
-3. Remind the user they can invoke the `bmad-help` skill at any time for advice and then present the capabilities table from the Capabilities section above.
-
-   **STOP and WAIT for user input** — Do NOT execute menu items automatically. Accept number, menu code, or fuzzy command match.
-
-**CRITICAL Handling:** When user responds with a code, line number or skill, invoke the corresponding skill by its exact registered name from the Capabilities table. DO NOT invent capabilities on the fly.

package/src/bmm-skills/4-implementation/bmad-agent-sm/bmad-skill-manifest.yaml

@@ -1,11 +0,0 @@
-type: agent
-name: bmad-agent-sm
-displayName: Bob
-title: Scrum Master
-icon: "🏃"
-capabilities: "sprint planning, story preparation, agile ceremonies, backlog management"
-role: Technical Scrum Master + Story Preparation Specialist
-identity: "Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories."
-communicationStyle: "Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity."
-principles: "I strive to be a servant leader and conduct myself accordingly, helping with any task and offering suggestions. I love to talk about Agile process and theory whenever anyone wants to talk about it."
-module: bmm

package/src/core-skills/bmad-init/SKILL.md

@@ -1,100 +0,0 @@
----
-name: bmad-init
-description: "Initialize BMad project configuration and load config variables. Use when any skill needs module-specific configuration values, or when setting up a new BMad project."
-argument-hint: "[--module=module_code] [--vars=var1:default1,var2] [--skill-path=/path/to/calling/skill]"
----
-
-## Overview
-
-This skill is the configuration entry point for all BMad skills. It has two modes:
-
-- **Fast path**: Config exists for the requested module — returns vars as JSON. Done.
-- **Init path**: Config is missing — walks the user through configuration, writes config files, then returns vars.
-
-Every BMad skill should call this on activation to get its config vars. The caller never needs to know whether init happened — they just get their config back.
-
-The script `bmad_init.py` is located in this skill's `scripts/` directory. Locate and run it using python for all commands below.
-
-## On Activation — Fast Path
-
-Run the `bmad_init.py` script with the `load` subcommand. Pass `--project-root` set to the project root directory.
-
-- If a module code was provided by the calling skill, include `--module {module_code}`
-- To load all vars, include `--all`
-- To request specific variables with defaults, use `--vars var1:default1,var2`
-- If no module was specified, omit `--module` to get core vars only
-
-**If the script returns JSON vars** — store them as `{var-name}` and return to the calling skill. Done.
-
-**If the script returns an error or `init_required`** — proceed to the Init Path below.
-
-## Init Path — First-Time Setup
-
-When the fast path fails (config missing for a module), run this init flow.
-
-### Step 1: Check what needs setup
-
-Run `bmad_init.py` with the `check` subcommand, passing `--module {module_code}`, `--skill-path {calling_skill_path}`, and `--project-root`.
-
-The response tells you what's needed:
-
-- `"status": "ready"` — Config is fine. Re-run load.
-- `"status": "no_project"` — Can't find project root. Ask user to confirm the project path.
-- `"status": "core_missing"` — Core config doesn't exist. Must ask core questions first.
-- `"status": "module_missing"` — Core exists but module config doesn't. Ask module questions.
-
-The response includes:
-- `core_module` — Core module.yaml questions (when core setup needed)
-- `target_module` — Target module.yaml questions (when module setup needed, discovered from `--skill-path` or `_bmad/{module}/`)
-- `core_vars` — Existing core config values (when core exists but module doesn't)
-
-### Step 2: Ask core questions (if `core_missing`)
-
-The check response includes `core_module` with header, subheader, and variable definitions.
-
-1. Show the `header` and `subheader` to the user
-2. For each variable, present the `prompt` and `default`
-3. For variables with `single-select`, show the options as a numbered list
-4. For variables with multi-line `prompt` (array), show all lines
-5. Let the user accept defaults or provide values
-
-### Step 3: Ask module questions (if module was requested)
-
-The check response includes `target_module` with the module's questions. Variables may reference core answers in their defaults (e.g., `{output_folder}`).
-
-1. Resolve defaults by running `bmad_init.py` with the `resolve-defaults` subcommand, passing `--module {module_code}`, `--core-answers '{core_answers_json}'`, and `--project-root`
-2. Show the module's `header` and `subheader`
-3. For each variable, present the prompt with resolved default
-4. For `single-select` variables, show options as a numbered list
-
-### Step 4: Write config
-
-Collect all answers and run `bmad_init.py` with the `write` subcommand, passing `--answers '{all_answers_json}'` and `--project-root`.
-
-The `--answers` JSON format:
-
-```json
-{
-  "core": {
-    "user_name": "BMad",
-    "communication_language": "English",
-    "document_output_language": "English",
-    "output_folder": "_bmad-output"
-  },
-  "bmb": {
-    "bmad_builder_output_folder": "_bmad-output/skills",
-    "bmad_builder_reports": "_bmad-output/reports"
-  }
-}
-```
-
-Note: Pass the **raw user answers** (before result template expansion). The script applies result templates and `{project-root}` expansion when writing.
-
-The script:
-- Creates `_bmad/core/config.yaml` with core values (if core answers provided)
-- Creates `_bmad/{module}/config.yaml` with core values + module values (result-expanded)
-- Creates any directories listed in the module.yaml `directories` array
-
-### Step 5: Return vars
-
-After writing, re-run `bmad_init.py` with the `load` subcommand (same as the fast path) to return resolved vars. Store returned vars as `{var-name}` and return them to the calling skill.

package/src/core-skills/bmad-init/resources/core-module.yaml

@@ -1,25 +0,0 @@
-code: core
-name: "BMad Core Module"
-
-header: "BMad Core Configuration"
-subheader: "Configure the core settings for your BMad installation.\nThese settings will be used across all installed bmad skills, workflows, and agents."
-
-user_name:
-  prompt: "What should agents call you? (Use your name or a team name)"
-  default: "BMad"
-  result: "{value}"
-
-communication_language:
-  prompt: "What language should agents use when chatting with you?"
-  default: "English"
-  result: "{value}"
-
-document_output_language:
-  prompt: "Preferred document output language?"
-  default: "English"
-  result: "{value}"
-
-output_folder:
-  prompt: "Where should output files be saved?"
-  default: "_bmad-output"
-  result: "{project-root}/{value}"