doccraft

# DocCraft

## Overview

Use this skill in two layers:

1. Build grounded text from source materials and a target framework.
2. If needed, create or revise the final `.docx` deliverable.

Keep Markdown or plain text as the working source of truth until the wording and structure are stable. Move into DOCX creation, formatting, tracked changes, or comments only after the content is sufficiently mature.

This skill vendors the DOCX capability locally. Do not assume a separate `$docx` skill is installed.

Some upload targets reject bundled OOXML schema files such as `.xsd`. When preparing a publishable package, use the packaged upload-safe variant from this skill. That variant keeps document generation and editing workflows, but omits the strict schema-validation bundle.

When the final deliverable is a Word document, always determine the format authority before finalization:

1. User-provided template or existing target document.
2. Explicit written formatting requirements from the user.
3. An accepted sample deliverable in the same domain.
4. The default format profile in this skill.

## Workflow Decision Tree

### A. Build a new document from existing materials

Use the source-grounded text workflow:

1. Normalize the task inputs.
2. Build a source manifest.
3. Create section briefs from the target outline.
4. Draft section files.
5. Run document-level consistency review.
6. Assemble the final Markdown or text output.

### B. Read, create, or edit a Word document

Use the DOCX workflows in this skill:

1. Read existing `.docx` content with `pandoc` when text extraction is enough.
2. Create a new `.docx` from scratch only after fully reading [docx-js.md](docx-js.md).
3. Edit or redline existing `.docx` files only after fully reading [ooxml.md](ooxml.md).
4. Default to tracked changes or comments for government, legal, academic, commercial, or third-party documents.

### C. Do both

Split the work into phases:

1. Draft and stabilize text first.
2. Freeze the source-ba...