some early doc updates

Author: Brian Madison

docs/explanation/custom-content-types.md

@@ -2,128 +2,79 @@
 title: "Custom Content"
 ---
 
-BMad supports several categories of custom content that extend the platform's capabilities — from simple personal agents to full-featured professional modules.
+BMad supports several categories of custom content that extend the platform's capabilities. This ranges from simple personal agents to full-featured professional modules.
 
-:::tip[Recommended Approach]
-Use the BMad Builder (BoMB) Module for guided workflows and expertise when creating custom content.
-:::
+## Overview
 
-This flexibility enables:
+This flexibility lets you:
 
-- Extensions and add-ons for existing modules (BMad Method, Creative Intelligence Suite)
+- Extensions and add-ons for existing modules
 - Completely new modules, workflows, templates, and agents outside software engineering
 - Professional services tools
-- Entertainment and educational content
-- Science and engineering workflows
-- Productivity and self-help solutions
 - Role-specific augmentation for virtually any profession
 
-## Categories
+:::tip[Recommended Approach]
+Use the BMad Builder (BoMB) Module for guided workflows and expertise when creating custom content.
+:::
+
+## Module Categories
 
-- [Categories](#categories)
-- [Custom Stand-Alone Modules](#custom-stand-alone-modules)
-- [Custom Add-On Modules](#custom-add-on-modules)
-- [Custom Global Modules](#custom-global-modules)
-- [Custom Agents](#custom-agents)
-  - [BMad Tiny Agents](#bmad-tiny-agents)
-  - [Simple and Expert Agents](#simple-and-expert-agents)
-- [Custom Workflows](#custom-workflows)
+BMad supports three types of custom modules, plus standalone agents and workflows:
 
-## Custom Stand-Alone Modules
+- **Custom Stand-Alone Modules**: Independent systems that work on their own
+- **Custom Add-On Modules**: Extensions that enhance another module
+- **Custom Global Modules**: Cross-cutting functionality for all installed content
 
-Custom modules range from simple collections of related agents, workflows, and tools designed to work independently, to complex, expansive systems like the BMad Method or even larger applications.
+### Custom Stand-Alone Modules
 
-Custom modules are [installable](/docs/how-to/installation/install-custom-modules.md) using the standard BMad method and support advanced features:
+Custom modules range from simple collections of related agents, workflows, and tools to complex systems like the BMad Method or even larger applications.
 
-- Optional user information collection during installation/updates
+Custom modules are [installable](/docs/how-to/install-custom-modules.md) using the standard BMad method and support advanced features:
+
+- Optional user information collection during installation and updates
 - Versioning and upgrade paths
 - Custom installer functions with IDE-specific post-installation handling (custom hooks, subagents, or vendor-specific tools)
 - Ability to bundle specific tools such as MCP, skills, execution libraries, and code
 
-## Custom Add-On Modules
-
-Custom Add-On Modules contain specific agents, tools, or workflows that expand, modify, or customize another module but cannot exist or install independently. These add-ons provide enhanced functionality while leveraging the base module's existing capabilities.
+### Custom Add-On Modules
 
-Examples include:
+Custom add-on modules contain specific agents, tools, or workflows that expand, modify, or customize another module. They cannot be installed or used independently. These add-ons provide enhanced functionality by using the base module's existing capabilities.
 
-- Alternative implementation workflows for BMad Method agents
-- Framework-specific support for particular use cases
-- Game development expansions that add new genre-specific capabilities without reinventing existing functionality
+Examples include the core module, which is always installed and provides all agents with party mode and advanced elicitation capabilities.
 
 Add-on modules can include:
 
 - Custom agents with awareness of the target module
 - Access to existing module workflows
-- Tool-specific features such as rulesets, hooks, subprocess prompts, subagents, and more
-
-## Custom Global Modules
-
-Similar to Custom Stand-Alone Modules, but designed to add functionality that applies across all installed content. These modules provide cross-cutting capabilities that enhance the entire BMad ecosystem.
-
-Examples include:
-
-- The core module, which is always installed and provides all agents with party mode and advanced elicitation capabilities
-- Installation and update tools that work with any BMad method configuration
+- Tool-specific features such as rulesets, hooks, subprocess prompts, and subagents
 
-Upcoming standards will document best practices for building global content that affects installed modules through:
+### Custom Global Modules
 
-- Custom content injections
-- Agent customization auto-injection
-- Tooling installers
+Global modules are similar to stand-alone modules, but they add functionality that applies across all installed content. These modules provide cross-cutting capabilities that enhance the entire BMad ecosystem.
 
-## Custom Agents
+Examples include installation and update tools that work with any BMad method configuration.
 
-Custom Agents can be designed and built for various use cases, from one-off specialized agents to more generic standalone solutions.
+## Building Blocks
 
-### BMad Tiny Agents
+### Custom Agents
 
-Personal agents designed for highly specific needs that may not be suitable for sharing. For example, a team management agent living in an Obsidian vault that helps with:
-
-- Team coordination and management
-- Understanding team details and requirements
-- Tracking specific tasks with designated tools
-
-These are simple, standalone files that can be scoped to focus on specific data or paths when integrated into an information vault or repository.
-
-### Simple and Expert Agents
-
-The distinction between simple and expert agents lies in their structure:
-
-**Simple Agent:**
-
-- Single file containing all prompts and configuration
-- Self-contained and straightforward
-
-**Expert Agent:**
-
-- Similar to simple agents but includes a sidecar folder
-- Sidecar folder contains additional resources: custom prompt files, scripts, templates, and memory files
-- When installed, the sidecar folder (`[agentname]-sidecar`) is placed in the user memory location
-- has metadata type: expert
-
-:::note[Key Distinction]
-The key distinction is the presence of a sidecar folder. As web and consumer agent tools evolve to support common memory mechanisms, storage formats, and MCP, the writable memory files will adapt to support these evolving standards.
-:::
-
-Custom agents can be:
+Custom agents can be designed and built for various use cases, from one-off specialized agents to more generic standalone solutions. Custom agents can be:
 
 - Used within custom modules
 - Designed as standalone tools
-- Integrated with existing workflows and systems, if this is to be the case, should also include a module: <module name> if a specific module is intended for it to require working with
+- Integrated with existing workflows and modules
 
-## Custom Workflows
+### Custom Workflows
 
-Workflows are powerful, progressively loading sequence engines capable of performing tasks ranging from simple to complex, including:
+Workflows range from simple single-file prompts to progressively loading sequence engines that can perform tasks including:
 
-- User engagements
+- User facilitation and engagement
 - Business processes
 - Content generation (code, documentation, or other output formats)
+- Utility functions and processes
 
-A custom workflow created outside of a larger module can still be distributed and used without associated agents through:
-
-- Slash commands
-- Manual command/prompt execution when supported by tools
+A custom workflow created outside of a larger module can still be distributed and used without associated agents through slash commands.
 
 :::tip[Core Concept]
-At its core, a custom workflow is a single or series of prompts designed to achieve a specific outcome.
+At its core, a custom workflow is a single prompt or series of prompts made to achieve a specific outcome. It is installed as a command or a skill.
 :::

docs/explanation/customize-workflows.md

@@ -18,13 +18,3 @@ Workflow customization will allow you to:
 - **Add Hooks** - Inject custom behavior before/after workflow steps
 - **Extend Workflows** - Create new workflows based on existing ones
 - **Override Behavior** - Customize workflow logic for your project's needs
-
-## For Now
-
-While workflow customization is in development, you can:
-
-- **Create Custom Workflows** - Use the BMad Builder to create entirely new workflows
-- **Customize Agents** - Modify agent behavior using [Agent Customization](/docs/how-to/customization/customize-agents.md)
-- **Provide Feedback** - Share your workflow customization needs with the community
-
-**In the meantime:** Learn how to [create custom workflows](/docs/explanation/bmad-builder/index.md) from scratch.