assemble-document

Merge chapter part markdown files into a single document with validated references.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill assemble-document-ameng2001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assemble-document
Source: https://github.com/Ameng2001/astra-studio-plugins/tree/main/studio-docs/skills/assemble-document
Command: npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill assemble-document-ameng2001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning multiple independently written document chapters into a single, publication-ready markdown file that matches blueprint rules, with consistent numbering, terminology, and validated internal references.

Core Features & Use Cases

  • Doc-plan driven assembly: Reads a doc plan YAML to determine chapter order, required/optional status, and the governing blueprint.
  • Merge + numbering harmonization: Concatenates chapter parts in the correct sequence and fixes chapter/section heading numbering to follow blueprint conventions.
  • Quality guardrails: Checks for missing required chapters, verifies part files have meaningful content, and performs terminology consistency replacements (with code/table/special-block exclusions).
  • Structure validation: Validates cross-references (chapters/sections/tables/figures/appendices) and assigns sequential figure/table numbers within chapters.
  • Compliance checking + reporting: Runs blueprint compliance checks (citations, required sections, diagrams/tables counts, word count/timeline expectations) and writes both the final document and a quality report.

Quick Start

Run assemble-document on your doc plan path so it merges all written chapter parts into a final markdown document and produces a quality report.

Frequently Asked Questions about assemble-document

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

FAQPage Schema
How do I merge multiple markdown chapter files into a single publication-ready document?

To merge markdown chapter files into a single document, use a doc-plan driven assembly tool that reads a YAML plan, orders parts directories, harmonizes numbering, and outputs a publication-ready file with a quality report.

How does cross-reference validation work when assembling markdown files?

Cross-reference validation checks internal links to chapters, sections, tables, figures, and appendices against the doc-plan order, ensuring structural integrity and assigning sequential numbering within the merged document.

Can I enforce terminology consistency across independently written markdown chapters?

Yes, terminology consistency is enforced during markdown document assembly by applying targeted text replacements, while explicitly excluding code blocks, tables, and special blocks to preserve formatting.

What is the best way to check blueprint compliance for a multi-chapter markdown document?

The best way to check blueprint compliance is to run an automated assembly that verifies required chapters, citation rules, diagram counts, and word limits, generating a structured quality report alongside the output document.

How do I fix figure and table numbering when concatenating separate markdown parts?

Figure and table numbering is fixed during the merge process by assigning sequential numbers within each chapter, ensuring the final concatenated markdown adheres to blueprint conventions.

What happens if required chapters are missing from the doc plan YAML during assembly?

If required chapters are missing from the doc plan YAML, the assembly process triggers a quality guardrail that detects the omission and logs the error in the generated structured quality report.