BMAD-METHOD/.kilocode/rules/memory-bank/product.md

2.1 KiB

Product Context

Problem Statement

Traditional AI tools provide direct answers, replacing human thinking rather than amplifying it. This leads to:

  • Dependency on AI-generated solutions without understanding
  • Generic, one-size-fits-all approaches that don't adapt to project needs
  • Loss of human creativity and strategic thinking
  • Lack of structured methodology for complex software projects

Solution

BMAD-METHOD provides a structured framework where:

  1. AI agents guide rather than dictate - Through strategic questioning and expert facilitation
  2. Workflows adapt to complexity - 5 levels (0-4) from quick fixes to enterprise scale
  3. Specialized agents provide domain expertise - PM, Architect, Developer, etc.
  4. Reflection drives better solutions - Guided thinking processes unlock creativity

Target Users

  • Software developers building web, mobile, embedded, or game applications
  • Teams needing standardized AI collaboration workflows
  • Project managers orchestrating complex development efforts
  • Creators building custom AI agents and workflows (via BMB)

User Experience Goals

For Developers

  • Quick activation of specialized agents in their IDE
  • Minimal overhead for small tasks (Level 0-1)
  • Comprehensive support for complex projects (Level 3-4)
  • Seamless integration with existing workflows

For Teams

  • Consistent methodology across projects
  • Shared agent behaviors via customization files
  • Update-safe configuration that persists through versions
  • Multi-language support for global teams

For Module Creators

  • Clear framework for building custom agents
  • Workflow creation tools and templates
  • Packaging system for distributing modules
  • Integration with BMAD-CORE infrastructure

Key Differentiators

  1. Scale-Adaptive: Automatically adjusts workflow complexity
  2. Reflection-Driven: Guides human thinking vs replacing it
  3. Agent-Specialized: Domain experts vs general-purpose chat
  4. Update-Safe: Customizations survive framework updates
  5. Framework-First: Extensible platform vs closed system