The Official BMad-Method Masterclass (The Complete IDE Workflow)

BMAD Method Installation and Setup in Cloud Code
📌 The BMAD method can be installed in any IDE of choice using `npx bmad-method install`.
⚙️ The installation process allows for sharding the PRD and Architecture into smaller documents to maximize agent context.
💻 The demonstration focuses on installing and using the BMAD method entirely within Cloud Code in VS Code for a greenfield development of a simple To-Do application.
⚡ A full installation can be completed in as fast as 5 seconds after the initial explanation.

Phase 1: Ideation and Brainstorming (The Analyst Agent)
💡 The Analyst Agent (Mary) is highlighted as potentially the most special agent, useful for brainstorming beyond just software development.
🧠 The brainstorming feature offers 20 techniques, including Six Thinking Hats and Five W's, guiding the user through focused ideation.
📄 Brainstorming results are artifacted into a Brainstorming Document stored in the `Docs` folder, which is then used to kickstart the next stage.
🎯 The goal of this phase is to move from a vague idea toward transforming task management into behavioral intelligence.

Phase 2: Defining Requirements (Product Manager Agent)
🔑 The Product Manager (PM) Agent translates the Project Brief (or initial idea) into a Product Requirements Document (PRD), defining functional and non-functional requirements structured into Epics and User Stories.
✂️ A key function of the PM is to help maintain MVP scope by distinguishing necessary features from post-MVP additions.
🚀 Advanced elicitation techniques like "If Only Hindsight is 20/20" are used to stress-test requirements and cut unnecessary scope early.
🔗 User stories are generated with meticulous dependency checking, ensuring perfect sequential order for development agents.

Phase 3: Technical Design (Architect Agent)
🏗️ The Architect Agent generates high-level architecture, sequence diagrams, and critical documentation like the Tech Stack, Source Tree, and Coding Standards.
🧱 Sharding the architecture into smaller documents (using `shard doc` command) ensures developer agents only load necessary context, preventing context pollution.
📝 The Tech Stack document forces agents to stick to specified library versions, preventing unexpected package installations during development.
🗣️ Users are encouraged to engage in dialogue with the architect (e.g., asking "Why are you using this database?") to learn real-world software development principles.

Phase 4: Development and Quality Assurance
🧑‍💻 The Developer Agent (James) receives detailed, self-contained stories from the Scrum Master and uses the architecture context to implement features step-by-step.
🧪 After development, the QA Agent (Quinn) performs a deep examination, verifying compliance checks and improvements against the story and source code.
🔄 The workflow strongly recommends clearing context (new chat) between agents to minimize load and maintain focus, even when using powerful local models like Claude Opus.
➡️ The process flows sequentially: Analyst $\rightarrow$ PM $\rightarrow$ Architect $\rightarrow$ Scrum Master $\rightarrow$ Developer $\rightarrow$ QA.

Key Points & Insights
➡️ The BMAD method emphasizes an interactive, coaching approach where the LLM pushes the user for better ideas, rather than just executing commands ("elevating yourself, learning, and also elevating the LLM").
➡️ All major stages—brainstorming, PRD creation, and architecture—can be performed entirely within the IDE using Cloud Code, eliminating the need for the web interface.
➡️ Context management is crucial: Users must actively clear or refresh the chat context between major workflow steps to keep the LLM focused and leverage sharded documents effectively.
➡️ Utilize the Advanced Elicitations provided by each agent (PM, Architect) to challenge the LLM's output and force deeper analysis, ensuring high-quality foundational documents.

📸 Video summarized with SummaryTube.com on Dec 16, 2025, 14:55 UTC