Creating Modules with BMAD (CCS)

🎥 Video lesson — video not yet migrated (source Skool video id: ea771bb0683a423b918f7d5c6ca05023).

Creating Custom Modules with BMAD — Building a Content Creation Suite

This video walks through the full process of creating a custom BMAD module from scratch. We build a complete Content Creation Suite with 6 agents and 22 workflows, covering everything from the initial brief to the final module structure.

BMAD Hierarchy (4 Levels):

  • Modules — groups of agents (e.g. Content Creation Module)
  • Agents — specialised roles within a module (e.g. Content Strategist, Copywriter, Video Editor)
  • Commands — actions agents can execute (e.g. /create-prd, /validate-prd)
  • Workflows — the underlying processes that commands trigger (e.g. competitive research, quality review)

What we build in this video:

  1. A comprehensive module brief covering vision, target users, agents, workflows, tools, and scenarios
  2. A full Content Creation Suite module containing 6 agent placeholders (Content Strategist, Copywriter, Creative Director, Video Editor, Editor, Publisher), 22 workflow specs, configuration files, help registry, README, and build tracking

Step-by-step process:

  1. Run /bmad-help and describe your goal — it tells you exactly what commands to run next
  2. Run /bmb-create-module-brief to brainstorm and plan your module (choose interactive or express mode)
  3. Run /bmb-create-module and pass in the brief using the @filename syntax to build the full structure

Express vs Interactive brainstorming:

  • Interactive — the system walks you through step by step. Best when you're still figuring out what you want
  • Express — you provide bulk information upfront. Best when you have a clear vision already

Claude Code modes covered:

  • Default — asks permission for every action (best for beginners)
  • Accept Edits — auto-approves many edits (intermediate)
  • Planning Mode — Claude thinks more carefully before responding
  • --dangerously-skip-permissions — bypasses all prompts including file deletion (advanced users with 20-50+ hours experience only)

Bonus: Setting up Exa MCP for web research Exa gives Claude the ability to search the web and scrape documentation during your workflows. Install it through Claude Desktop settings (Developer → Local MCP Servers → paste config JSON), then import into Claude Code with claude mcp add --from claude-desktop. Activate it in conversation by asking Claude to "use Exa MCP to research [topic]."

Key tips from the video:

  • Don't skip the module brief — it takes 15-30 minutes but saves enormous time during the build
  • Give Claude as much context as possible during planning. The more detail you front-load, the better the output
  • There's close to 0% chance everything works perfectly first time. The real process is: build → use on real content → notice what's off → edit → repeat for 1-3 weeks. Only then does it become truly agentic
  • If you don't understand a tool or concept, just ask Claude. You've got an expert teacher available 24/7

Useful commands:

  • /bmad-help — guidance on which commands to run for your goal
  • /bmb-create-module-brief — create the module planning document
  • /bmb-create-module — build the full module from a brief
  • /bmb-create-agent — create an individual agent (covered in the next video)
  • /resume — pick up a previous Claude Code conversation after restarting
  • /clear — clear current conversation context
  • @filename — reference and pass files into a conversation

Next up: Creating the first agent — the Content Strategist.

← Previous
Next →