bmad-shard-doc

Split large markdown documents into smaller files by level 2 headings.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-shard-doc-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-shard-doc
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-shard-doc
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-shard-doc-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of breaking a long markdown document into smaller, organized files so large specs are easier to navigate, review, and maintain.

Core Features & Use Cases

  • Section-Based Splitting: Shards a source markdown file into separate files using level 2 headings by default.
  • Workflow Orchestration: Guides the full process from source selection and destination setup through execution, verification, and handling the original file.
  • Practical Use Case: Use it to split a large architecture document, product spec, or planning artifact into a folder of smaller sections for easier collaboration.

Quick Start

Use the bmad-shard-doc skill to split the markdown file at your chosen path into a new sharded folder and follow the prompts for the original document.

Frequently Asked Questions about bmad-shard-doc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a large markdown document into smaller files?

Splitting a large markdown document into smaller files is done by sharding the source file using level 2 headings, creating organized section files in a destination folder for easier navigation and review.

What is the best way to break down long repository docs for easier maintenance?

Breaking down long repository docs is best handled by a sharding workflow that parses level 2 sections into individual files, guiding you from source selection through output verification and original file cleanup.

Can I automate document splitting for architecture specs and planning artifacts?

Automating document splitting for architecture specs and planning artifacts is supported through a workflow that orchestrates parser execution, destination folder handling, and a delete, move, or keep decision for the original file.

Does markdown sharding work with any heading level or only level 2 sections?

Markdown sharding applies to level 2 section headings by default to separate a source file into organized section files. The workflow focuses on this structure to ensure consistent sharding of large documents.

What happens to the original markdown file after the sharding process is complete?

After the sharding process is complete, the workflow prompts you to make a delete, move, or keep decision for the original markdown file once the output section files are verified in the destination folder.

When do I need to shard markdown files instead of keeping them as single documents?

You need to shard markdown files when large design specs, product specs, or planning artifacts become difficult to navigate, review, and maintain, requiring organized level 2 section sharding for better collaboration.