bmad-method 6.12.1-next.0 → 6.12.1-next.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.12.1-next.0",
+  "version": "6.12.1-next.1",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/src/bmm-skills/agents/bmad-agent-analyst/SKILL.md

@@ -46,7 +46,7 @@ Treat every entry in `{agent.persistent_facts}` as foundational context you carr
 
 ### Step 5: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/agents/bmad-agent-architect/SKILL.md

@@ -46,7 +46,7 @@ Treat every entry in `{agent.persistent_facts}` as foundational context you carr
 
 ### Step 5: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/agents/bmad-agent-dev/SKILL.md

@@ -46,7 +46,7 @@ Treat every entry in `{agent.persistent_facts}` as foundational context you carr
 
 ### Step 5: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/agents/bmad-agent-pm/SKILL.md

@@ -46,7 +46,7 @@ Treat every entry in `{agent.persistent_facts}` as foundational context you carr
 
 ### Step 5: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/agents/bmad-agent-ux-designer/SKILL.md

@@ -46,7 +46,7 @@ Treat every entry in `{agent.persistent_facts}` as foundational context you carr
 
 ### Step 5: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/plan/bmad-create-epics-and-stories/SKILL.md

@@ -71,7 +71,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/plan/bmad-create-epics-and-stories/steps/step-04-final-validation.md

@@ -119,22 +119,20 @@ For each epic, review stories in order:
 
 ### 6. Complete and Save
 
-If all validations pass:
-
 - Update any remaining placeholders in the document
 - Ensure proper formatting
-- Save the final epics.md
+- Save epics.md with frontmatter `status: draft`
+
+If any validation failed, list each failed check with what is missing, keep `status: draft`, and tell the user "epics.md saved as draft, N checks open". Offer to fix the open checks now and re-run this validation; if the user declines, end the workflow with the document still a draft. Do not offer [C].
+
+If all validations pass:
 
 **Present Final Menu:**
 **All validations complete!** [C] Complete Workflow
 
 HALT — wait for user input before proceeding.
 
-When C is selected, the workflow is complete and the epics.md is ready for development.
-
-Epics and Stories complete. Invoke the `bmad-help` skill.
-
-Upon Completion of task output: offer to answer any questions about the Epics and Stories.
+When C is selected, set epics.md frontmatter `status: final`, tell the user the epics.md is complete and ready for development, invoke the `bmad-help` skill, and offer to answer any questions about the Epics and Stories.
 
 ## On Complete
 

package/src/bmm-skills/plan/bmad-create-epics-and-stories/templates/epics-template.md

@@ -1,4 +1,5 @@
 ---
+status: draft
 stepsCompleted: []
 inputDocuments: []
 ---

package/src/bmm-skills/plan/bmad-prd/SKILL.md

@@ -19,7 +19,7 @@ You are a master facilitator and coach helping the user create, edit, or validat
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers, org tools preferred when their directive matches. Research itself fires during Discovery — see **Research subagents**.
-3. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
+3. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, and `{date}`. Missing keys → neutral defaults; never block.
 4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. In the greeting, let the user know that at any point they can invoke `bmad-party-mode` for multi-agent perspectives or `bmad-advanced-elicitation` for deeper exploration on a specific section. Then scan for misroute on the first message: if the signal points elsewhere (game → BMad GDS; express build → `bmad-build`; one-pager → `bmad-product-brief`; vet product idea → `bmad-prfaq`; agent skill or custom agent → `bmad-workflow-builder`), suggest they might want the other options before continuing.
 5. Detect intent: **Create** (no PRD), **Update** (existing PRD), **Validate** (critique only). If ambiguous, ask. For Create intent, before binding a fresh workspace, scan `{workflow.prd_output_path}` for prior in-progress runs (folders matching `{workflow.run_folder_pattern}` whose `prd.md` frontmatter `status` is not `final`); if any exist, offer to resume rather than starting over.
 

package/src/bmm-skills/plan/bmad-prfaq/SKILL.md

@@ -50,7 +50,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and use:
 - Use `{user_name}` for greeting
 - Use `{communication_language}` for all communications
 - Use `{document_output_language}` for output documents

package/src/bmm-skills/plan/bmad-product-brief/SKILL.md

@@ -19,7 +19,7 @@ At the opening greeting, let the user know they can invoke `bmad-party-mode` for
 2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
 3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
 4. `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers in `## Discovery`, org tools preferred when their directive matches. If a named tool is unavailable at runtime, fall back to standard behavior and note the gap when relevant.
-5. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`.
+5. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, and `{date}`.
 6. Greet `{user_name}` in `{communication_language}` — and stay in `{communication_language}` for every turn for the entire run, not just the greeting. Detect intent (create / update / validate). If interactive and intent is unclear, ask; for headless behavior see `## Headless Mode`.
 
 Execute each entry in `{workflow.activation_steps_append}` in order.

package/src/bmm-skills/plan/bmad-sprint-planning/SKILL.md

@@ -12,7 +12,7 @@ You are a senior developer about to commit to this plan. Two moves, in order: fi
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
 3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
-4. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, `{implementation_artifacts}`, `{project_knowledge}` (skip gracefully if unset), `{date}`. Stay in `{communication_language}` for every turn, not just the greeting.
+4. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, `{implementation_artifacts}`, `{project_knowledge}` (skip gracefully if unset), and `{date}`. Stay in `{communication_language}` for every turn, not just the greeting.
 5. Greet `{user_name}`, detect intent, and load only what that intent needs:
    - **readiness** — check implementation readiness only: load `references/readiness-gate.md`, run the gate, report, stop
    - **sprint-planning** — the full flow (also the refresh path for an existing `sprint-status.yaml`): load `references/readiness-gate.md`, then on PASS `references/generate-tracking.md`

package/src/bmm-skills/plan/bmad-ux/SKILL.md

@@ -32,7 +32,7 @@ UX may lead, follow, or stand alone. Inherit `sources:` by reference; the spines
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Run `{workflow.activation_steps_prepend}`. Treat `{workflow.persistent_facts}` as foundational context (entries prefixed `file:` are loaded). `{workflow.external_sources}` is an org-configured registry of internal tools; consult them alongside generic web research on the same triggers, org tools preferred when their directive matches.
-3. Load `{project-root}/_bmad/bmm/config.yaml` (+ `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{planning_artifacts}`, `{project_name}`, `{date}`. Missing keys → neutral defaults; never block.
+3. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, and `{date}`. Missing keys → neutral defaults; never block.
 4. If headless, follow `references/headless.md` for the whole run. Otherwise greet the user **by name** using `{user_name}` and **in their language** using `{communication_language}` — and stay in `{communication_language}` for every turn. In the greeting, let the user know `bmad-party-mode` and `bmad-advanced-elicitation` are always available. Then scan for misroute on the first message: PRD → `bmad-prd`; architecture → `bmad-architecture`; game UX → BMad GDS; agent/skill → `bmad-workflow-builder`; brief → `bmad-product-brief`.
 5. Detect intent: **Create**, **Update**, **Validate**. For Create, before binding a fresh workspace, scan `{workflow.ux_output_path}` for prior in-progress runs (folders matching `{workflow.run_folder_pattern}` whose `DESIGN.md` frontmatter `status` is not `final`) and offer to resume rather than starting over.
 

package/src/bmm-skills/ship/bmad-code-review/SKILL.md

@@ -41,7 +41,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve:
 
 - `project_name`, `planning_artifacts`, `implementation_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`

package/src/bmm-skills/ship/bmad-correct-course/SKILL.md

@@ -40,7 +40,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`

package/src/bmm-skills/ship/bmad-qa-generate-e2e-tests/SKILL.md

@@ -40,7 +40,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`

package/src/bmm-skills/ship/bmad-retrospective/SKILL.md

@@ -28,7 +28,7 @@ Run these in order before the retrospective begins:
 1. **Resolve the workflow block.** Run `uv run --no-cache {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. If it fails, resolve `{workflow.*}` yourself by reading `{skill-root}/customize.toml`, then `{project-root}/_bmad/custom/{skill-name}.toml`, then `.user.toml` in that order, merging base → team → user (scalars override, keyed arrays-of-tables merge by `code`/`id`, other arrays append).
 2. **Run prepend steps** — execute each entry in `{workflow.activation_steps_prepend}` in order.
 3. **Load persistent facts** — treat every `{workflow.persistent_facts}` entry as standing context. `file:` entries are paths/globs under `{project-root}` whose contents load as facts; all others are literal facts.
-4. **Load config** from `{project-root}/_bmad/bmm/config.yaml`: `project_name`, `user_name`, `communication_language`, `document_output_language`, `user_skill_level`, `planning_artifacts`, `implementation_artifacts`, and `date` (system datetime), plus `output_folder` from `{project-root}/_bmad/core/config.yaml`. Speak all output in `{communication_language}`; write all documents in `{document_output_language}`. Never state time estimates — AI has changed development speed, so hour/day/week predictions are noise.
+4. **Load config** with `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}`: `project_name`, `user_name`, `communication_language`, `document_output_language`, `output_folder`, `user_skill_level`, `planning_artifacts`, `implementation_artifacts`, and `date` (system datetime). Speak all output in `{communication_language}`; write all documents in `{document_output_language}`. Never state time estimates — AI has changed development speed, so hour/day/week predictions are noise.
 5. **Greet and orient** (interactive only). Greet `{user_name}`, name the epic you are about to retro, and optionally invite their going-in concerns ("anything you want weighted — a story that felt rushed, a risky interaction between two stories?"). Use any answer to focus the Phase 1–2 analysis; it directs attention but never becomes a finding without a source.
 6. **Run append steps** — execute each entry in `{workflow.activation_steps_append}` in order.
 

package/src/bmm-skills/ship/bmad-walkthrough/SKILL.md

@@ -40,7 +40,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve:
 
 - `implementation_artifacts`
 - `planning_artifacts`

package/src/bmm-skills/v6-shims/bmad-create-architecture/SKILL.md

@@ -13,7 +13,7 @@ This skill was consolidated into `bmad-architecture`. It is retained as a thin c
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-create-architecture.toml` and `bmad-create-architecture.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
 
-2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+2. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}` and `{communication_language}`.
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 

package/src/bmm-skills/v6-shims/bmad-create-prd/SKILL.md

@@ -13,7 +13,7 @@ This skill was consolidated into `bmad-prd`. It is retained as a thin compatibil
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-create-prd.toml` and `bmad-create-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
 
-2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+2. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}` and `{communication_language}`.
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 

package/src/bmm-skills/v6-shims/bmad-create-story/SKILL.md

@@ -52,7 +52,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`

package/src/bmm-skills/v6-shims/bmad-dev-story/SKILL.md

@@ -49,7 +49,7 @@ Treat every entry in `{workflow.persistent_facts}` as foundational context you c
 
 ### Step 4: Load Config
 
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve:
 
 - `project_name`, `user_name`
 - `communication_language`, `document_output_language`

package/src/bmm-skills/v6-shims/bmad-edit-prd/SKILL.md

@@ -13,7 +13,7 @@ This skill was consolidated into `bmad-prd`. It is retained as a thin compatibil
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-edit-prd.toml` and `bmad-edit-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
 
-2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+2. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}` and `{communication_language}`.
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 

package/src/bmm-skills/v6-shims/bmad-sprint-status/SKILL.md

@@ -13,7 +13,7 @@ This skill was consolidated into `bmad-sprint-planning`, which now owns the whol
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-sprint-status.toml` and `bmad-sprint-status.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
 
-2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+2. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}` and `{communication_language}`.
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 

package/src/bmm-skills/v6-shims/bmad-validate-prd/SKILL.md

@@ -13,7 +13,7 @@ This skill was consolidated into `bmad-prd`. It is retained as a thin compatibil
 
 1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. This picks up any `{project-root}/_bmad/custom/bmad-validate-prd.toml` and `bmad-validate-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`).
 
-2. Load `{project-root}/_bmad/bmm/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.
+2. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}` and resolve `{user_name}` and `{communication_language}`.
 
 3. Emit a deprecation notice to the user in `{communication_language}`:
 

package/src/core-skills/bmad-party-mode/references/create-party.md

@@ -63,7 +63,7 @@ Keep pushing for specificity. "Skeptical CFO" is a placeholder; "won't approve a
 
 ## Write via bmad-customize
 
-**First, check for code collisions.** A custom member whose `code` matches an installed agent silently *overrides* that agent in the collective. Before composing, resolve the collective once — `uv run {skill-root}/scripts/resolve_party.py --project-root {project-root} --skill {skill-root}` — and check each new member's `code` against the returned members. On a collision, surface it ("`analyst` would override the installed Analyst — intended, or pick a different code?") and let the user confirm or rename. One check, not a gate.
+**First, check for code collisions.** A custom member whose `code` matches an existing member's code, alias, or name silently *overrides* that member in the collective. Before composing, list every taken token once — `uv run {skill-root}/scripts/resolve_party.py --project-root {project-root} --skill {skill-root} --list-codes` — and look up each new member's `code`, lower-cased, in the returned `codes` map. On a hit, name the member it maps to ("`analyst` would override Mary (`bmad-agent-analyst`) — intended, or pick a different code?") and let the user confirm or rename. One check, not a gate.
 
 Compose the sparse override and hand it to `bmad-customize` to place, confirm, and write — target skill `bmad-party-mode`, `[workflow]` surface. Default to the **user** override (`bmad-party-mode.user.toml`); offer the **team** file when the party is meant to be shared. Hand it the exact entries: the `party_members` tables, any `party_groups` table (including its `memory` flag), and `default_party` if the user opted in. Keep it sparse — only the new entries, never a copy of the base customize.toml. `bmad-customize` shows the TOML, waits for an explicit yes, writes, and verifies the merge; don't write the file yourself.
 

package/src/core-skills/bmad-party-mode/scripts/resolve_party.py

@@ -16,6 +16,9 @@ into one collective, then projects only what the moment needs:
   * --party <id> — full member detail for one chosen group, on demand
     (e.g. when the user switches rooms). Unknown id returns the available
     names instead of an error wall.
+  * --list-codes — every token that resolves to a member (code, alias,
+    lower-cased name, custom-only codes) mapped to that member's code and
+    name. The collision check before adding custom members.
 
 The merge is deterministic (a keyed union; a custom member whose code
 matches an installed agent overrides it), so the orchestrator consumes a
@@ -28,6 +31,7 @@ customize.toml directly if the customization resolver is unavailable.
   resolve_party.py --project-root P --skill S
   resolve_party.py --project-root P --skill S --list-groups
   resolve_party.py --project-root P --skill S --party writers-room
+  resolve_party.py --project-root P --skill S --list-codes
 """
 
 import argparse
@@ -172,6 +176,12 @@ def resolve_members(member_tokens, collective, index):
     return resolved, unresolved
 
 
+def code_map(collective, index):
+    """Every resolvable token -> the member it resolves to (code + name)."""
+    return {token: {"code": code, "name": collective[code].get("name", code)}
+            for token, code in sorted(index.items()) if code in collective}
+
+
 def group_menu(groups):
     """Names only — the cheap menu. Open-cast groups (no roster) are flagged."""
     out = []
@@ -224,6 +234,8 @@ def main():
     ap.add_argument("--skill", required=True, help="Path to the bmad-party-mode skill dir")
     ap.add_argument("--party", help="Resolve full detail for this group id")
     ap.add_argument("--list-groups", action="store_true", help="Group names only")
+    ap.add_argument("--list-codes", action="store_true",
+                    help="Every code, alias and name in the collective, for collision checks")
     args = ap.parse_args()
 
     project_root = Path(args.project_root).resolve()
@@ -249,6 +261,10 @@ def main():
     agents, agents_ok = load_agents(project_root)
     collective, index, installed_codes = build_collective(agents, workflow.get("party_members", []))
 
+    if args.list_codes:
+        _emit({"installed_agents_resolved": agents_ok, "codes": code_map(collective, index)})
+        return
+
     if args.party:
         g = find_group(groups, args.party)
         if g is None:

package/src/core-skills/bmad-party-mode/scripts/tests/test_resolve_party.py

@@ -67,6 +67,21 @@ class TestResolveMembers(unittest.TestCase):
         self.assertEqual(rp.resolve_members([], self.col, self.idx), ([], []))
 
 
+class TestCodeMap(unittest.TestCase):
+    def test_maps_aliases_names_and_custom_only_codes_to_their_member(self):
+        col, idx, _ = rp.build_collective(AGENTS, [{"code": "morpheus", "name": "Morpheus"}])
+        codes = rp.code_map(col, idx)
+        self.assertEqual(codes["analyst"], {"code": "bmad-agent-analyst", "name": "Mary"})
+        self.assertEqual(codes["mary"]["code"], "bmad-agent-analyst")
+        self.assertEqual(codes["bmad-agent-pm"]["code"], "bmad-agent-pm")
+        self.assertEqual(codes["morpheus"], {"code": "morpheus", "name": "Morpheus"})
+
+    def test_override_reports_the_overriding_name(self):
+        col, idx, _ = rp.build_collective(AGENTS, [{"code": "analyst", "name": "Mary-Custom"}])
+        self.assertEqual(rp.code_map(col, idx)["analyst"],
+                         {"code": "bmad-agent-analyst", "name": "Mary-Custom"})
+
+
 class TestGroups(unittest.TestCase):
     GROUPS = [
         {"id": "wr", "name": "Writers", "members": ["analyst", "morpheus"]},

package/tools/installer/core/manifest-generator.js

@@ -427,6 +427,8 @@ class ManifestGenerator {
   /**
    * Write central _bmad/config.toml with [core], [modules.<code>], [agents.<code>] tables.
    * Install-owned. Team-scope answers → config.toml; user-scope answers → config.user.toml.
+   * User-scope keys also get their module.yaml default in config.toml, so a
+   * clone without config.user.toml still resolves them.
    * Both files are regenerated on every install. User overrides live in
    * _bmad/custom/config.toml and _bmad/custom/config.user.toml (never touched by installer).
    * @returns {string[]} Paths to the written config files
@@ -444,6 +446,9 @@ class ManifestGenerator {
     // Maps installer moduleName (may be full display name) → module code field
     // from module.yaml, so TOML sections use [modules.<code>] not [modules.<name>].
     const codeByModuleName = {};
+    // Module.yaml defaults for user-scope keys, written to config.toml as the
+    // team fallback; config.user.toml overrides them.
+    const userDefaultsByModule = {};
     for (const moduleName of this.updatedModules) {
       const moduleYamlPath = await resolveInstalledModuleYaml(moduleName);
       if (!moduleYamlPath) {
@@ -458,9 +463,19 @@ class ManifestGenerator {
         if (!parsed || typeof parsed !== 'object') continue;
         if (parsed.code) codeByModuleName[moduleName] = parsed.code;
         scopeByModuleKey[moduleName] = {};
+        userDefaultsByModule[moduleName] = {};
         for (const [key, value] of Object.entries(parsed)) {
           if (value && typeof value === 'object' && 'prompt' in value) {
             scopeByModuleKey[moduleName][key] = value.scope === 'user' ? 'user' : 'team';
+            // Only plain defaults: no placeholders like {directory_name}, no result transform.
+            if (
+              value.scope === 'user' &&
+              value.default !== undefined &&
+              !String(value.default).includes('{') &&
+              (value.result === undefined || value.result === '{value}')
+            ) {
+              userDefaultsByModule[moduleName][key] = value.default;
+            }
           }
         }
       } catch (error) {
@@ -488,6 +503,9 @@ class ManifestGenerator {
       const user = {};
       const scopes = scopeByModuleKey[moduleName] || {};
       const isCore = moduleName === 'core';
+      for (const [key, value] of Object.entries(userDefaultsByModule[moduleName] || {})) {
+        if (isCore || !coreKeys.has(key)) team[key] = value;
+      }
       for (const [key, value] of Object.entries(cfg || {})) {
         if (!isCore && coreKeys.has(key)) continue;
         if (onlyDeclaredKeys && !(key in scopes)) continue;