bmad-shard-doc

Splitting large Markdown documents is done by using level-2 headings as boundaries to generate separate shard files. This process outputs an index.md file alongside per-section documents to improve readability, maintenance, and collaboration.

Organizing long Markdown documentation is best achieved by fragmenting the file by level-2 sections to create a predictable file structure. This approach automatically generates an index.md to summarize all shards and preserve navigability for easier review and versioning.

No, this Markdown sharding approach does not work with any heading level, as it specifically relies on a standard Markdown structure using level-2 headings as shard boundaries. Input validation ensures deterministic behavior based on this requirement.

Yes, you can automatically generate an index.md file when breaking down a Markdown document into shards. This index summarizes all the generated per-section files to preserve navigability across the fragmented documentation.

The main limitation of sharding Markdown files by section boundaries is the strict reliance on level-2 headings to determine file splits, meaning documents without this standard structure cannot be processed. The behavior is deterministic but constrained to this specific heading level.