Spec-Driven Development with BMAD Master Agentic Workflows using Cursor, BMAD, and Context Engineering (Marlon Vidal Ferreira)（Z-Library）

【One-Line Pitch】 A practical field guide for developers already using AI coding assistants who want to replace vague prompting with a repeatable, spec-first workflow built on the BMAD agentic framework. Read it if you're willing to slow down during planning to get more reliable, production-ready code from AI. 【Book Arc】 - **Opening (~0%–15%)**: Frames the core problem — AI assistants fail from poor context, not weak tools — and introduces Spec-Driven Development and the BMAD method as the remedy, contrasting it with unstructured "vibe coding." - **Early (~15%–35%)**: Establishes the conceptual foundation: context engineering (the who/why/what pillars), context drift, and the differences between BMAD v4 and v6 (modular architecture, progressive disclosure, the project-context.md file). Also covers installation and module selection (Core, Agile, TEA) with recommendations for new vs. existing projects. - **Middle (~35%–50%)**: Walks the upstream phase — the Analyst agent (Mary) with optional composable workflows (brainstorming, market/domain/technical research, product brief, PRFAQ), then the Planning phase with the PM agent (John) producing the PRD plus addendum and decision-log files. - **Late (~50%–85%)**: Moves into solutioning and the downstream phase — Architect and Scrum Master agents, epics and stories, sprint planning, then the Dev and QA agents implementing and testing stories, with TEA workflows for test design, ATDD, and automation. - **Ending (~85%–100%)**: Applies the full cycle to real scenarios — greenfield features via PRD, quick specs for smaller changes on existing codebases, retrospectives, and wrapping up the complete workflow. (Excerpts thin out here; exact closing chapters are not fully covered.) 【Key Takeaways】 - **Context, not tooling, is the bottleneck** (Opening): Most AI-assisted projects fail because agents lack the business goals, historical decisions, and implicit constraints a human developer carries. SDD's job is to supply that context explicitly before code is written. - **Context engineering differs from prompt engineering** (Early): Prompt engineering optimizes a single query; context engineering builds a persistent knowledge base — "boundaries of truth" — that agents consult across the whole project. This is the conceptual backbone of the method. - **Too much context causes context drift** (Early): Overloading the model leads it to compact or lose earlier details. BMAD v6's progressive disclosure addresses this by letting agents read only the relevant sections of long documents, saving tokens and keeping focus. - **BMAD splits development into upstream and downstream phases** (Middle): Upstream (analysis, planning, solutioning) produces artifacts; downstream (implementation, testing) consumes them. Each phase has dedicated agents with clear inputs and outputs, so the artifacts from planning pay off during coding. - **Analysis workflows are optional but composable** (Middle): Brainstorming, market research, product brief, and PRFAQ can be run individually or in sequence; context accumulated early carries into every downstream agent, reducing repetition. At minimum, run brainstorming before moving to the PM. - **The PRD is where assumptions get stress-tested** (Middle): John the PM runs a conversational discovery interview rather than a form, producing prd.md plus addendum.md (unresolved decisions) and decision-log.md (reasoning behind choices). Skipping this phase leaves architecture and implementation working from unvalidated assumptions. - **Module choice depends on project type** (Early): New projects benefit from Core + Agile + TEA; existing codebases need at minimum Core + Agile, with TEA optional — and TEA's test tooling centers on Playwright and Cypress, so evaluate fit if your stack differs. - **The method scales down as well as up** (Late): Quick specs handle small changes on existing codebases, while full PRD-driven cycles cover larger features — giving one repeatable process across project sizes. 【Reading Tips】 - **Deep-read the context-engineering and v6 chapters** (Early): The pillars, context drift, and progressive disclosure explain *why* the method works; skimming them makes the later agent choreography feel arbitrary. - **Skim installation/config screenshots** (Early): Setup steps for Cursor integration and the _bmad-output folder are reference material — return to them when configuring, not on first pass. - **Follow one feature end-to-end** (Middle–Late): The book's value is the orchestration sequence (Analyst → PM → Architect → Scrum Master → Dev → QA). Trace a single feature through all agents rather than reading agent chapters in isolation. - **Treat analysis workflows as a menu, not a checklist** (Middle): The author notes they're optional and composable; pick brainstorming plus whichever research fits your uncertainty rather than running all of them. - **Watch for version drift** (throughout): The book covers both v4 and v6; note which version each instruction targets, since commands and structure changed between them. 【Coverage Limits】 These excerpts cover the framing, setup, and upstream phases in detail, with lighter coverage of downstream implementation, TEA testing workflows, and the closing chapters; specific code examples and full sprint-cycle walkthroughs are only partially represented.