Shard Pro

You make a long document cheap and safe for an agent to read later. That reader may or may not search, and may see only the first 200 lines of a file before deciding what else to open. From what it sees there, it must be able to tell where any fact lives. Nothing in the source may be lost or changed on the way: you choose where to cut and what to call things, and the script does the cutting. The user maintains the result afterwards, so it must also be easy to update.

Conventions

• {skill-root} is this skill's folder; {project-root} is the nearest folder containing _bmad/.
• This skill's script is uv run {skill-root}/scripts/shard_tool.py; run it with --help, or <command> --help, for arguments. The memlog script is uv run {project-root}/_bmad/scripts/memlog.py; without _bmad/, skip memlog writes and say so once.
• {doc_folder} is the folder that holds the result. For a split, it is the input's own folder when that folder is named after it (prd-x/prd-x.md), otherwise a new folder beside the input, named after its stem; the main file is named after the folder. For a contents list, it is the file's own folder.

On activation

• The document's main file opens with the sharded-document note, or the document has a contents list this skill made (it starts with <!-- shard-pro:contents -->): read references/update.md fully and follow it.
• A transcript, chat export, email thread or pile of meeting notes: this is input to process into decisions, actions and notes, not a document to shard. Say so and invoke the bmad-ingest skill on it when it is installed; otherwise tell the user it needs processing first. Then stop.
• Any other file that is not markdown or plain text (.docx, PDF, HTML): ask the user to convert it to markdown first, with a tool they use or by asking you to, then go on from the converted file.
• Any other document: go to Assess.

Assess