bmad-shard-doc

To split a large markdown document, this skill automatically shards the file into smaller, organized components based on level 2 headers. It structures the output into a directory and generates an index file to maintain the original document hierarchy.

Modularizing long-form technical specifications is best achieved by sharding the monolithic markdown file into individual chapters. This process breaks down oversized files into smaller, manageable components to improve version control and readability.

Automated sharding handles document hierarchy by splitting content at level 2 headers and automatically generating an index file. This index preserves the structural relationships of the original markdown document after it is divided into smaller files.

Yes, you need the @kayvan/markdown-tree-parser package available in your environment to execute the sharding process. This dependency is required to parse the markdown structure and split the document by level 2 headers.

You should break down a monolithic markdown file when it becomes oversized and difficult to navigate, edit, or maintain. Sharding is ideal for massive technical specifications needing improved readability and modular version control.