Large-scale project documentation management (such as directory structure, including PRD, front-end and back-end development documents, design documents, etc.)

[safa1018]

Describe your idea
A clear and concise description of what you'd like to see added or changed.

Why is this needed?
Explain the problem this solves or the benefit it brings to the BMad community.

How should it work?
Describe your proposed solution. If you have ideas on implementation, share them here.

PR
If you'd like to contribute, please indicate you're working on this or link to your PR. Please review CONTRIBUTING.md — contributions are always welcome!

Additional context
Add any other context, screenshots, or links that help explain your idea.

[coderabbitai]

🔗 Related PRs

#1309 - docs: comprehensive documentation overhaul with style guide expansion [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[safa1018]

In large-scale projects, there are many modules and functionality points, and a single MD document cannot cover everything.

For example, the product documentation needs to include general rules, concept explanations, business process diagrams, data and state definitions, page interaction explanations, boundary declarations, etc.
The back-end development documentation needs to cover database rules, data and states, technical solution explanations, APIs, and so on.
The design documentation, including front-end-related aspects, is similar.

[bmadcode]

right now the current state of workflows is they create something that is middle ground between a human readable useful document and what is needed for the llm. The future enhancement in the works is to rework each workflow to output to a folder its artifacts instead of a single document when appropriate, have it be optimized for human readability and then have an output that is a distillate for llm consumption of just the critical details needed for downstream import.

[safa1018]

very good

[safa1018]

@bmadcode I also hope version management can be supported.

For example, support creating a new version, 和 allow organizing the current development version into the existing version list.
Support summarizing the content of this version into existing long-term documentation.

[bmadcode]

that might get a bit beyond - but the idea will be all artifacts should be versioned controlled just like any other code artifact giving full change history for every artifacts