Epics and Sprints génération

[nzerrai]

Description

Epics and sprints are generated by default in monolithic files. In my case, I use this for projects with a minimum of 8 epics and 60 user stories. Monolithic files are large and lack visibility. Why not generate one epic per file by default and each sprint per folder, with one file per story? I think this should be prioritized over monolithic files. It improves visibility and saves on tokens.

Steps to reproduce

NA

Expected behavior

NA

Actual behavior

NA

Screenshots

Which module is this for?

BMad Method (BMM) - Core Framework

BMad Version

6.8.0

Which AI IDE are you using?

Claude Code

Operating System

macOS

Relevant log output

Confirm

• I've searched for existing issues
• I'm using the latest version

[coderabbitai]

🔗 Related PRs

#1826 - feat(workflows): add brownfield epic scoping to detect file churn (#1823) [merged]
#2218 - feat(quick-dev): add epic context compilation to step-01 [merged]
#2446 - fix(bmad-create-epics-and-stories): discover bmad-ux spine outputs [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!

[bmadcode]

this is coming with or potentially for v7, planned on the roadmap. Expected to be within the next few weeks at most.

[nzerrai]

I used two patch files to directly modify the base skills. I didn't use the customization skill because the monolithic code is hardcoded into the skills that generates epics and stories and

bmad-epics-consumers-sharding.md
bmad-sprints-stories-folder.md

sprints.