manage-document-projectslisted

# Manage Document Projects Manage document families as versioned projects. Keep Markdown and structured data canonical; treat PDF, DOCX, ODT, and HTML as generated artifacts. ## Start safely 1. Run `bash scripts/setup.sh` and review the dry-run. 2. Run `bash scripts/setup.sh --apply` only with explicit authorization to install packages, create or update the fixed workspace configuration, and link the skill. 3. Run the setup again whenever the workspace or optional-tool choices change. It is idempotent and verifies the resulting environment. Read [references/setup.md](references/setup.md) when installing, repairing, or moving the skill. ## Build a document project 1. Identify the project instance, project type, jurisdiction, and effective date. 2. Separate instance data from reusable templates, clauses, and output profiles. 3. Record the project-type and template versions used by every generated document. 4. Render Jinja2 variables into canonical Markdown. 5. Reject unresolved variables and invalid data before conversion. 6. Select an output profile using [references/output-formats.md](references/output-formats.md). 7. Keep concrete Markdown under the configured project location and printable or shareable derivatives under the configured deliverables location. Never ingest from deliverables or overwrite signed or externally reviewed documents. 8. Open the result in its real viewer and inspect pagination, headings, tables, images, signatur