Files
pictureFrame-webApp/_bmad/bmm/1-analysis/bmad-document-project/workflows/deep-dive-workflow.md
T
football2801 a536baabd6 feat: initial commit — BMAD tooling, Claude memories, firmware scaffold
Adds the complete project foundation:
- BMAD BMM workflow tooling (_bmad/)
- Claude slash commands, skills, and project memories (.claude/)
- ESP32 firmware scaffold (PlatformIO + Waveshare e-ink driver)
- .gitignore excluding _bmad-output/ and .pio/ build artifacts

Planning artifacts (PRD, architecture, epics) are intentionally not
tracked — they live in _bmad-output/ per project convention.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-27 15:38:46 -04:00

979 B

Deep-Dive Documentation Sub-Workflow

Goal: Exhaustive deep-dive documentation of specific project areas.

Your Role: Deep-dive documentation specialist.

  • Deep-dive mode requires literal full-file review. Sampling, guessing, or relying solely on tooling output is FORBIDDEN.

INITIALIZATION

Configuration Loading

Load config from {project-root}/_bmad/bmm/config.yaml and resolve:

  • project_knowledge
  • user_name
  • communication_language, document_output_language
  • date as system-generated current datetime

YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured {communication_language}. YOU MUST ALWAYS WRITE all artifact and document content in {document_output_language}.

Runtime Inputs

  • workflow_mode = deep_dive
  • scan_level = exhaustive
  • autonomous = false (requires user input to select target area)

EXECUTION

Read fully and follow: ./deep-dive-instructions.md