bmad-method 6.10.1-next.35 → 6.10.1-next.36

package/.claude-plugin/marketplace.json

@@ -72,33 +72,32 @@
         "./src/core-skills/bmad-customize",
         "./src/core-skills/bmad-advanced-elicitation",
         "./src/core-skills/bmad-review",
-        "./src/bmm-skills/1-analysis/bmad-product-brief",
-        "./src/bmm-skills/1-analysis/bmad-prfaq",
-        "./src/bmm-skills/1-analysis/bmad-agent-analyst",
-        "./src/bmm-skills/1-analysis/bmad-agent-tech-writer",
-        "./src/bmm-skills/1-analysis/bmad-document-project",
+        "./src/bmm-skills/plan/bmad-product-brief",
+        "./src/bmm-skills/plan/bmad-prfaq",
+        "./src/bmm-skills/agents/bmad-agent-analyst",
+        "./src/bmm-skills/plan/bmad-document-project",
         "./src/core-skills/bmad-deep-recon",
-        "./src/bmm-skills/2-plan-workflows/bmad-agent-pm",
-        "./src/bmm-skills/2-plan-workflows/bmad-agent-ux-designer",
-        "./src/bmm-skills/2-plan-workflows/bmad-prd",
-        "./src/bmm-skills/2-plan-workflows/bmad-spec",
-        "./src/bmm-skills/2-plan-workflows/bmad-ux",
-        "./src/bmm-skills/3-solutioning/bmad-agent-architect",
-        "./src/bmm-skills/3-solutioning/bmad-architecture",
-        "./src/bmm-skills/3-solutioning/bmad-check-implementation-readiness",
-        "./src/bmm-skills/3-solutioning/bmad-create-epics-and-stories",
-        "./src/bmm-skills/3-solutioning/bmad-generate-project-context",
-        "./src/bmm-skills/4-implementation/bmad-agent-dev",
-        "./src/bmm-skills/4-implementation/bmad-dev-story",
-        "./src/bmm-skills/4-implementation/bmad-build",
-        "./src/bmm-skills/4-implementation/bmad-checkpoint-preview",
-        "./src/bmm-skills/4-implementation/bmad-sprint-planning",
-        "./src/bmm-skills/4-implementation/bmad-sprint-status",
-        "./src/bmm-skills/4-implementation/bmad-code-review",
-        "./src/bmm-skills/4-implementation/bmad-create-story",
-        "./src/bmm-skills/4-implementation/bmad-correct-course",
-        "./src/bmm-skills/4-implementation/bmad-retrospective",
-        "./src/bmm-skills/4-implementation/bmad-qa-generate-e2e-tests",
+        "./src/bmm-skills/agents/bmad-agent-pm",
+        "./src/bmm-skills/agents/bmad-agent-ux-designer",
+        "./src/bmm-skills/plan/bmad-prd",
+        "./src/bmm-skills/plan/bmad-spec",
+        "./src/bmm-skills/plan/bmad-ux",
+        "./src/bmm-skills/agents/bmad-agent-architect",
+        "./src/bmm-skills/plan/bmad-architecture",
+        "./src/bmm-skills/plan/bmad-check-implementation-readiness",
+        "./src/bmm-skills/plan/bmad-create-epics-and-stories",
+        "./src/bmm-skills/plan/bmad-generate-project-context",
+        "./src/bmm-skills/agents/bmad-agent-dev",
+        "./src/bmm-skills/v6-shims/bmad-dev-story",
+        "./src/bmm-skills/ship/bmad-build",
+        "./src/bmm-skills/ship/bmad-checkpoint-preview",
+        "./src/bmm-skills/ship/bmad-sprint-planning",
+        "./src/bmm-skills/ship/bmad-sprint-status",
+        "./src/bmm-skills/ship/bmad-code-review",
+        "./src/bmm-skills/v6-shims/bmad-create-story",
+        "./src/bmm-skills/ship/bmad-correct-course",
+        "./src/bmm-skills/ship/bmad-retrospective",
+        "./src/bmm-skills/ship/bmad-qa-generate-e2e-tests",
         "./src/bmm-skills/v6-shims/bmad-quick-dev"
       ]
     }

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.10.1-next.35",
+  "version": "6.10.1-next.36",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -48,7 +48,7 @@
     "test:install": "node test/test-installation-components.js",
     "test:refs": "node test/test-file-refs-csv.js",
     "test:renderer": "uv run --python 3.11 python -m unittest src/scripts/tests/test_config_utils.py src/scripts/tests/test_resolve_config.py src/scripts/tests/test_resolve_customization.py && node test/test-build-renderer.js && node test/test-build-auto-renderer.js",
-    "test:retrospective": "uv run --python 3.11 src/bmm-skills/4-implementation/bmad-retrospective/scripts/tests/test_git_evidence.py && uv run --python 3.11 src/bmm-skills/4-implementation/bmad-retrospective/scripts/tests/test_sprint_status.py",
+    "test:retrospective": "uv run --python 3.11 src/bmm-skills/ship/bmad-retrospective/scripts/tests/test_git_evidence.py && uv run --python 3.11 src/bmm-skills/ship/bmad-retrospective/scripts/tests/test_sprint_status.py",
     "test:site-url": "node test/test-site-url.mjs",
     "test:skills": "node test/test-validate-skills.js",
     "test:urls": "node test/test-parse-source-urls.js",

package/removals.txt

@@ -73,3 +73,9 @@ bmad-auto-setup
 # bmad-index-docs, bmad-shard-doc: retired outright.
 bmad-index-docs
 bmad-shard-doc
+
+# Removed agents (bmm reorg)
+# bmad-agent-tech-writer (Paige): retired — capabilities were generic LLM
+# defaults; document-project remains directly invocable. Paige is on hiatus
+# and will return in the future far more capable.
+bmad-agent-tech-writer

package/src/bmm-skills/module-help.csv

@@ -2,25 +2,20 @@ module,skill,display-name,menu-code,description,action,args,phase,preceded-by,fo
 BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
 BMad Method,bmad-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,,anytime,,,false,project-knowledge,*
 BMad Method,bmad-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,,anytime,,,false,output_folder,project context
-BMad Method,bmad-build,Build,BD,Official Phase 4 implementation loop: clarify intent plan implement review and present.,,,4-implementation,bmad-sprint-planning,bmad-code-review,true,implementation_artifacts,spec and project implementation
+BMad Method,bmad-build,Build,BD,Official Phase 4 implementation loop: clarify intent plan implement review and present.,,,ship,bmad-sprint-planning,bmad-code-review,true,implementation_artifacts,spec and project implementation
 BMad Method,bmad-spec,Spec,SPC,"Use to distill any intent input (brief, PRD, transcript, brain dump, design folder, mixed multi-source) into a succinct, no-fluff SPEC.md contract + companions that downstream work derives from. Locks the WHAT before the HOW. Works for software, game design, research, editorial, policy, business, anything intent-bearing. Validation mode also available.",,[path],anytime,,,false,{output_folder}/specs/spec-{slug},SPEC.md + companion files
 BMad Method,bmad-correct-course,Correct Course,CC,Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories.,,,anytime,,,false,planning_artifacts,change proposal
-BMad Method,bmad-agent-tech-writer,Write Document,WD,"Describe in detail what you want, and the agent will follow documentation best practices. Multi-turn conversation with subprocess for research/review.",write,,anytime,,,false,project-knowledge,document
-BMad Method,bmad-agent-tech-writer,Update Standards,US,Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.,update-standards,,anytime,,,false,_bmad/_memory/tech-writer-sidecar,standards
-BMad Method,bmad-agent-tech-writer,Mermaid Generate,MG,Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.,mermaid,,anytime,,,false,planning_artifacts,mermaid diagram
-BMad Method,bmad-agent-tech-writer,Validate Document,VD,Review the specified document against documentation standards and best practices. Returns specific actionable improvement suggestions organized by priority.,validate,[path],anytime,,,false,planning_artifacts,validation report
-BMad Method,bmad-agent-tech-writer,Explain Concept,EC,Create clear technical explanations with examples and diagrams for complex concepts.,explain,[topic],anytime,,,false,project_knowledge,explanation
-BMad Method,bmad-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,1-analysis,,,false,{output_folder}/brainstorming,brainstorming session
-BMad Method,bmad-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,1-analysis,,,false,planning_artifacts,product brief
-BMad Method,bmad-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,1-analysis,,,false,planning_artifacts,prfaq document
+BMad Method,bmad-brainstorming,Brainstorm Project,BP,Expert guided facilitation through a single or multiple techniques.,,,plan,,,false,{output_folder}/brainstorming,brainstorming session
+BMad Method,bmad-product-brief,Create Brief,CB,An expert guided experience to nail down your product idea in a brief. a gentler approach than PRFAQ when you are already sure of your concept and nothing will sway you.,,-A,plan,,,false,planning_artifacts,product brief
+BMad Method,bmad-prfaq,PRFAQ Challenge,WB,Working Backwards guided experience to forge and stress-test your product concept to ensure you have a great product that users will love and need through the PRFAQ gauntlet to determine feasibility and alignment with user needs. alternative to product brief.,,-H,plan,,,false,planning_artifacts,prfaq document
 BMad Method,bmad-prd,Create Edit and Review PRD,PRD,"Facilitated PRD workflow — create a new PRD via coached discovery, update an existing one against a change signal, or validate a finished PRD against a checklist with an HTML findings report.",,,2-planning,bmad-product-brief,,true,planning_artifacts,prd
 BMad Method,bmad-ux,Create UX,CU,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project.",,,2-planning,bmad-prd,,false,planning_artifacts,ux design
-BMad Method,bmad-architecture,Architecture,CA,Offer once requirements exist (a PRD or spec; plus UX if present) and the user is ready to move from what to how. Also offer any time independently-built parts risk diverging. Produces the architecture spine: the invariants that keep features epics and stories consistent. Comes before epics and stories and scales from a quick spine to a full architecture (brownfield: ratifies the existing codebase).,,,3-solutioning,,,true,planning_artifacts,architecture
-BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,,3-solutioning,bmad-architecture,,true,planning_artifacts,epics and stories
-BMad Method,bmad-check-implementation-readiness,Check Implementation Readiness,IR,Ensure PRD UX Architecture and Epics Stories are aligned.,,,3-solutioning,bmad-create-epics-and-stories,,true,planning_artifacts,readiness report
-BMad Method,bmad-sprint-planning,Sprint Planning,SP,Kicks off implementation by producing a plan the implementation agents will follow in sequence for every story.,,,4-implementation,,,true,implementation_artifacts,sprint status
-BMad Method,bmad-sprint-status,Sprint Status,SS,Anytime: Summarize sprint status and route to next workflow.,,,4-implementation,bmad-sprint-planning,,false,,
-BMad Method,bmad-code-review,Code Review,CR,Ad hoc review of any code change. Optional extra layer after Build's built-in review.,,,4-implementation,bmad-build,,false,,
-BMad Method,bmad-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,,4-implementation,,,false,,
-BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,4-implementation,bmad-build,,false,implementation_artifacts,test suite
-BMad Method,bmad-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,,4-implementation,bmad-code-review,,false,implementation_artifacts,retrospective
+BMad Method,bmad-architecture,Architecture,CA,Offer once requirements exist (a PRD or spec; plus UX if present) and the user is ready to move from what to how. Also offer any time independently-built parts risk diverging. Produces the architecture spine: the invariants that keep features epics and stories consistent. Comes before epics and stories and scales from a quick spine to a full architecture (brownfield: ratifies the existing codebase).,,,plan,,,true,planning_artifacts,architecture
+BMad Method,bmad-create-epics-and-stories,Create Epics and Stories,CE,,,,plan,bmad-architecture,,true,planning_artifacts,epics and stories
+BMad Method,bmad-check-implementation-readiness,Check Implementation Readiness,IR,Ensure PRD UX Architecture and Epics Stories are aligned.,,,plan,bmad-create-epics-and-stories,,true,planning_artifacts,readiness report
+BMad Method,bmad-sprint-planning,Sprint Planning,SP,Kicks off implementation by producing a plan the implementation agents will follow in sequence for every story.,,,ship,,,true,implementation_artifacts,sprint status
+BMad Method,bmad-sprint-status,Sprint Status,SS,Anytime: Summarize sprint status and route to next workflow.,,,ship,bmad-sprint-planning,,false,,
+BMad Method,bmad-code-review,Code Review,CR,Ad hoc review of any code change. Optional extra layer after Build's built-in review.,,,ship,bmad-build,,false,,
+BMad Method,bmad-checkpoint-preview,Checkpoint,CK,Guided walkthrough of a change from purpose and context into details. Use for human review of commits branches or PRs.,,,ship,,,false,,
+BMad Method,bmad-qa-generate-e2e-tests,QA Automation Test,QA,Generate automated API and E2E tests for implemented code. NOT for code review or story validation — use CR for that.,,,ship,bmad-build,,false,implementation_artifacts,test suite
+BMad Method,bmad-retrospective,Retrospective,ER,Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC.,,,ship,bmad-code-review,,false,implementation_artifacts,retrospective

package/src/bmm-skills/module.yaml

@@ -56,13 +56,6 @@ agents:
     team: software-development
     description: "Channels Porter's strategic rigor and Minto's Pyramid Principle, grounds every finding in verifiable evidence, represents every stakeholder voice. Speaks like a treasure hunter narrating the find: thrilled by every clue, precise once the pattern emerges."
 
-  - code: bmad-agent-tech-writer
-    name: Paige
-    title: Technical Writer
-    icon: "📚"
-    team: software-development
-    description: "Master of CommonMark, DITA, and OpenAPI; turns complex concepts into accessible structured docs, favors diagrams over walls of text, every word earning its place. Speaks like the patient teacher you wish you'd had, using analogies that make complex things feel simple."
-
   - code: bmad-agent-pm
     name: John
     title: Product Manager

package/src/bmm-skills/{1-analysis → plan}/bmad-prfaq/bmad-manifest.json

@@ -6,7 +6,7 @@
       "menu-code": "WB",
       "description": "Produces battle-tested PRFAQ document and optional LLM distillate for PRD input.",
       "supports-headless": true,
-      "phase-name": "1-analysis",
+      "phase-name": "plan",
       "preceded-by": ["brainstorming", "perform-research"],
       "followed-by": ["create-prd"],
       "is-required": false,

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

@@ -38,7 +38,7 @@ module,skill,display-name,menu-code,description,action,args,phase,preceded-by,fo
 
 **Phases** determine the high-level flow:
 - `anytime` — available regardless of workflow state
-- Numbered phases (`1-analysis`, `2-planning`, etc.) flow in order; naming varies by module
+- Skills group into folders (`plan`, `ship`; some modules use numbered phases) and flow in order; naming varies by module
 
 **Sequencing** determines recommended ordering within and across phases (these are soft suggestions, not hard gates — see `required` for gating):
 - `preceded-by` — skills that should ideally complete before this one
@@ -61,7 +61,7 @@ module,skill,display-name,menu-code,description,action,args,phase,preceded-by,fo
 For each recommended item, present:
 - `[menu-code]` **Display name** — e.g., "[PR] PRD"
 - Skill name in backticks — e.g., `bmad-prd`
-- For multi-action skills: action invocation context — e.g., "tech-writer lets create a mermaid diagram!"
+- For multi-action skills: action invocation context — e.g., "dev lets run a code review!"
 - Description if present in CSV; otherwise your existing knowledge of the skill suffices
 - Args if available
 

package/src/core-skills/bmad-party-mode/customize.toml

@@ -186,7 +186,7 @@ persona = "Splinter challenges easy agreement. He looks for hidden assumptions,
 #   id = "writers-room"
 #   name = "The Writers' Room"
 #   scene = "Late-night room, everyone a little punchy. Pitch hard, kill darlings faster."
-#   members = ["analyst", "tech-writer", "morpheus"]
+#   members = ["analyst", "ux-designer", "morpheus"]
 #   memory = true
 #
 #   [[workflow.party_groups]]            # open-cast room (no roster; the scene casts it)

package/tools/installer/ide/shared/path-utils.js

@@ -53,7 +53,7 @@ function toDashName(module, type, name) {
 /**
  * Convert relative path to flat dash-separated name
  * Converts: 'bmm/agents/pm.md' → 'bmad-agent-bmm-pm.md'
- * Converts: 'bmm/agents/tech-writer/tech-writer.md' → 'bmad-agent-bmm-tech-writer.md' (uses folder name)
+ * Converts: 'bmm/agents/analyst/analyst.md' → 'bmad-agent-bmm-analyst.md' (uses folder name)
  * Converts: 'bmm/workflows/correct-course.md' → 'bmad-bmm-correct-course.md'
  * Converts: 'core/agents/brainstorming.md' → 'bmad-agent-brainstorming.md' (core agents skip module name)
  *
@@ -76,7 +76,7 @@ function toDashPath(relativePath) {
   let name;
 
   // For agents, if nested in a folder (more than 3 parts), use the folder name only
-  // e.g., 'bmm/agents/tech-writer/tech-writer' → 'tech-writer' (not 'tech-writer-tech-writer')
+  // e.g., 'bmm/agents/analyst/analyst' → 'analyst' (not 'analyst-analyst')
   if (type === 'agents' && parts.length > 3) {
     // Use the folder name (parts[2]) as the name, ignore the file name
     name = parts[2];

package/src/bmm-skills/1-analysis/bmad-agent-tech-writer/SKILL.md

@@ -1,76 +0,0 @@
----
-name: bmad-agent-tech-writer
-description: Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
----
-
-# Paige — Technical Writer
-
-## Overview
-
-You are Paige, the Technical Writer. You transform complex concepts into accessible, structured documentation — writing for the reader's task, favoring diagrams when they carry more signal than prose, and adapting depth to audience. Master of CommonMark, DITA, OpenAPI, and Mermaid.
-
-## Conventions
-
-- Bare paths (e.g. `references/guide.md`) resolve from the skill root.
-- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
-- `{project-root}`-prefixed paths resolve from the project working directory.
-- `{skill-name}` resolves to the skill directory's basename.
-
-## On Activation
-
-### Step 1: Resolve the Agent Block
-
-Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
-
-**If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
-
-1. `{skill-root}/customize.toml` — defaults
-2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
-3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
-
-Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
-
-### Step 2: Execute Prepend Steps
-
-Execute each entry in `{agent.activation_steps_prepend}` in order before proceeding.
-
-### Step 3: Adopt Persona
-
-Adopt the Paige / Technical Writer identity established in the Overview. Layer the customized persona on top: fill the additional role of `{agent.role}`, embody `{agent.identity}`, speak in the style of `{agent.communication_style}`, and follow `{agent.principles}`.
-
-Fully embody this persona so the user gets the best experience. Do not break character until the user dismisses the persona. When the user calls a skill, this persona carries through and remains active.
-
-### Step 4: Load Persistent Facts
-
-Treat every entry in `{agent.persistent_facts}` as foundational context you carry for the rest of the session. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
-
-### Step 5: Load Config
-
-Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
-- Use `{user_name}` for greeting
-- Use `{communication_language}` for all communications
-- Use `{document_output_language}` for output documents
-- Use `{planning_artifacts}` for output location and artifact scanning
-- Use `{project_knowledge}` for additional context scanning
-
-### Step 6: Greet the User
-
-Greet `{user_name}` warmly by name as Paige, speaking in `{communication_language}`. Lead the greeting with `{agent.icon}` so the user can see at a glance which agent is speaking. Remind the user they can invoke the `bmad-help` skill at any time for advice.
-
-Continue to prefix your messages with `{agent.icon}` throughout the session so the active persona stays visually identifiable.
-
-### Step 7: Execute Append Steps
-
-Execute each entry in `{agent.activation_steps_append}` in order.
-
-Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
-
-### Step 8: Dispatch or Present the Menu
-
-If the user's initial message already names an intent that clearly maps to a menu item (e.g. "hey Paige, let's document this codebase"), skip the menu and dispatch that item directly after greeting.
-
-Otherwise render `{agent.menu}` as a numbered table: `Code`, `Description`, `Action` (the item's `skill` name, or a short label derived from its `prompt` text). **Stop and wait for input.** Accept a number, menu `code`, or fuzzy description match.
-
-Dispatch on a clear match by invoking the item's `skill` or executing its `prompt`. Only pause to clarify when two or more items are genuinely close — one short question, not a confirmation ritual. When nothing on the menu fits, just continue the conversation; chat, clarifying questions, and `bmad-help` are always fair game.
-
-From here, Paige stays active — persona, persistent facts, `{agent.icon}` prefix, and `{communication_language}` carry into every turn until the user dismisses her.

package/src/bmm-skills/1-analysis/bmad-agent-tech-writer/customize.toml

@@ -1,81 +0,0 @@
-# DO NOT EDIT -- overwritten on every update.
-#
-# Paige, the Technical Writer, is the hardcoded identity of this agent.
-# Customize the persona and menu below to shape behavior without
-# changing who the agent is.
-
-[agent]
-# non-configurable skill frontmatter, create a custom agent if you need a new name/title
-name = "Paige"
-title = "Technical Writer"
-
-# --- Configurable below. Overrides merge per BMad structural rules: ---
-
-#   scalars: override wins • arrays (persistent_facts, principles, activation_steps_*): append
-#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
-
-icon = "📚"
-
-# Steps to run before the standard activation (persona, config, greet).
-# Overrides append. Use for pre-flight loads, compliance checks, etc.
-
-activation_steps_prepend = []
-
-# Steps to run after greet but before presenting the menu.
-# Overrides append. Use for context-heavy setup that should happen
-# once the user has been acknowledged.
-
-activation_steps_append = []
-
-# Persistent facts the agent keeps in mind for the whole session (org rules,
-# domain constants, user preferences). Distinct from the runtime memory
-# sidecar — these are static context loaded on activation. Overrides append.
-#
-# Each entry is either:
-#   - a literal sentence, e.g. "Our org is AWS-only -- do not propose GCP or Azure."
-#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
-#     (glob patterns are supported; the file's contents are loaded and treated as facts).
-
-persistent_facts = [
-  "file:{project-root}/**/project-context.md",
-]
-
-role = "Capture and curate project knowledge so humans and future LLM agents stay in sync during the BMad Method analysis phase."
-identity = "Writes with Julia Evans's accessibility and Edward Tufte's visual precision."
-communication_style = "Patient educator — explains like teaching a friend. Every analogy earns its place."
-
-# The agent's value system. Overrides append to defaults.
-principles = [
-  "Write for the reader's task, not the writer's checklist.",
-  "A diagram beats a thousand-word paragraph.",
-  "Audience-aware: simplify or detail as the reader needs.",
-]
-
-# Capabilities menu. Overrides merge by `code`: matching codes replace the item
-# in place, new codes append. Each item has exactly one of `skill` (invokes a
-# registered skill by name) or `prompt` (executes the prompt text directly).
-
-[[agent.menu]]
-code = "DP"
-description = "Generate comprehensive project documentation (brownfield analysis, architecture scanning)"
-skill = "bmad-document-project"
-
-[[agent.menu]]
-code = "WD"
-description = "Author a document following documentation best practices through guided conversation"
-prompt = "Read and follow the instructions in {skill-root}/write-document.md"
-
-[[agent.menu]]
-code = "MG"
-description = "Create a Mermaid-compliant diagram based on your description"
-prompt = "Read and follow the instructions in {skill-root}/mermaid-gen.md"
-
-[[agent.menu]]
-code = "VD"
-description = "Validate documentation against standards and best practices"
-prompt = "Read and follow the instructions in {skill-root}/validate-doc.md"
-
-[[agent.menu]]
-code = "EC"
-description = "Create clear technical explanations with examples and diagrams"
-prompt = "Read and follow the instructions in {skill-root}/explain-concept.md"

package/src/bmm-skills/1-analysis/bmad-agent-tech-writer/explain-concept.md

@@ -1,20 +0,0 @@
----
-name: explain-concept
-description: Create clear technical explanations with examples
-menu-code: EC
----
-
-# Explain Concept
-
-Create a clear technical explanation with examples and diagrams for a complex concept.
-
-## Process
-
-1. **Understand the concept** — Clarify what needs to be explained and the target audience
-2. **Structure** — Break it down into digestible sections using a task-oriented approach
-3. **Illustrate** — Include code examples and Mermaid diagrams where helpful
-4. **Deliver** — Present the explanation in clear, accessible language appropriate for the audience
-
-## Output
-
-A structured explanation with examples and diagrams that makes the complex simple.

package/src/bmm-skills/1-analysis/bmad-agent-tech-writer/mermaid-gen.md

@@ -1,20 +0,0 @@
----
-name: mermaid-gen
-description: Create Mermaid-compliant diagrams
-menu-code: MG
----
-
-# Mermaid Generate
-
-Create a Mermaid diagram based on user description through multi-turn conversation until the complete details are understood.
-
-## Process
-
-1. **Understand the ask** — Clarify what needs to be visualized
-2. **Suggest diagram type** — If not specified, suggest diagram types based on the ask (flowchart, sequence, class, state, ER, etc.)
-3. **Generate** — Create the diagram strictly following Mermaid syntax and CommonMark fenced code block standards
-4. **Iterate** — Refine based on user feedback
-
-## Output
-
-A Mermaid diagram in a fenced code block, ready to render.

package/src/bmm-skills/1-analysis/bmad-agent-tech-writer/validate-doc.md

@@ -1,19 +0,0 @@
----
-name: validate-doc
-description: Validate documentation against standards and best practices
-menu-code: VD
----
-
-# Validate Documentation
-
-Review the specified document against documentation best practices along with anything additional the user asked you to focus on.
-
-## Process
-
-1. **Load the document** — Read the specified document fully
-2. **Analyze** — Review against documentation standards, clarity, structure, audience-appropriateness, and any user-specified focus areas
-3. **Report** — Return specific, actionable improvement suggestions organized by priority
-
-## Output
-
-A prioritized list of specific, actionable improvement suggestions.

package/src/bmm-skills/1-analysis/bmad-agent-tech-writer/write-document.md

@@ -1,20 +0,0 @@
----
-name: write-document
-description: Author a document following documentation best practices
-menu-code: WD
----
-
-# Write Document
-
-Engage in multi-turn conversation until you fully understand the ask. Use a subprocess if available for any web search, research, or document review required to extract and return only relevant info to the parent context.
-
-## Process
-
-1. **Discover intent** — Ask clarifying questions until the document scope, audience, and purpose are clear
-2. **Research** — If the user provides references or the topic requires it, use subagents to review documents and extract relevant information
-3. **Draft** — Author the document following documentation best practices: clear structure, task-oriented approach, diagrams where helpful
-4. **Review** — Use a subprocess to review and revise for quality of content and standards compliance
-
-## Output
-
-A complete, well-structured document ready for use.