Beta removes generate-project-context workflow but implementation workflows still depend on project-context.md

[mjesuele]

Summary

The generate-project-context workflow was removed in the beta release (clean install), but multiple implementation-phase workflows still glob for **/project-context.md and load it as foundational context. There is no replacement workflow that produces this file.

What was removed

• _bmad/bmm/workflows/generate-project-context/workflow.md
• _bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md
• _bmad/bmm/workflows/generate-project-context/steps/step-02-generate.md
• _bmad/bmm/workflows/generate-project-context/steps/step-03-complete.md
• _bmad/bmm/workflows/generate-project-context/project-context-template.md
• Corresponding slash command entry

What still references project-context.md

These workflows declare project_context: "**/project-context.md" as a variable or reference it in their steps:

• dev-story (workflow.yaml) — loads as foundational reference
• quick-dev (step-01-mode-detection.md) — "Check if {project_context} exists... load it as a foundational reference for ALL implementation decisions"
• quick-spec (step-01-understand.md) — "Check for **/project-context.md - if it exists, skim for patterns and conventions"
• create-story (workflow.yaml)
• code-review (workflow.yaml)
• sprint-planning (workflow.yaml)
• dev-story checklist — "Only uses dependencies specified in story or project-context.md"

document-project is not a replacement

The document-project workflow (which still exists) serves a different purpose — it's a brownfield codebase scanner that produces index.md and scan reports for understanding an existing codebase. The old generate-project-context workflow produced a concise, LLM-optimized rules document (critical patterns, anti-patterns, technology constraints) that agents reference during implementation.

These are complementary tools, not substitutes:

Aspect	generate-project-context (removed)	document-project (exists)
Purpose	Lean rules for AI agent implementation	Comprehensive codebase documentation
Output	project-context.md (~350 lines)	index.md + scan reports
Audience	AI agents writing code	Humans/AI understanding existing code
Content	Anti-patterns, type rules, naming conventions, critical constraints	Architecture, file structure, dependencies

Expected behavior

Either:

1. Restore the generate-project-context workflow (or a modernized equivalent), or
2. Remove the project-context.md references from implementation workflows, or
3. Integrate project-context generation into an existing workflow (e.g., as a mode of document-project or output of architecture/PRD workflows)

Environment

• BMad Method version: 6.0.0-Beta.2
• Upgraded from: alpha.23 (where the workflow still existed)
• IDE: Claude Code

[jheyworth]

@mjesuele
This is by design as part of the upgrading to new workflow functionality.

It's on the roadmap for project-context to be reinstated shortly.

[bmadcode]

Consolidated into #1138 which covers integration issues including the missing generate-project-context workflow dependency problem.

[bmadcode]

this has been readded, and will be in the next version bump