sop-writer

Update revision date and version metadata across one or many SOPs in the current project, then optionally recompile. Reads the Typst frontmatter (or a leading metadata block) of each target document, increments the revision (semver-style: minor by default, patch/major on request), updates the date to today, and writes back. Use when the user has reviewed a set of procedures and wants to mark them as a fresh revision.

Concatenate a configured list of SOPs and flowcharts into a single printable PDF binder, with optional cover page, table of contents, and consistent page numbering across the bundle. The set of documents and binder metadata (title, cover image, footer text) is defined in `binders.yaml` in the project root. Use when the user wants to produce a printed binder — e.g. "household emergency binder", "kitchen procedures", "first-aid kit reference".

Compile a single SOP or flowchart in the current project to PDF. For SOPs, runs `typst compile`. For flowcharts, first renders the Mermaid/D2 source to SVG (via mmdc or d2), then compiles the Typst wrapper that embeds it. Outputs to the project's `output/` directory by default. Use when the user wants to produce or refresh a single printable PDF.

Restructure raw source material — a URL, pasted text, a PDF, or a markdown file — into a properly formatted SOP using one of the built-in templates. Reads the source, extracts the procedural content, maps it into the chosen template's section structure, and writes a new Typst SOP file in the project. Use when the user has reference material (e.g. a Red Cross first-aid page, a manufacturer manual, a wiki article) and wants to turn it into a printable household SOP.

Scaffold a new decision flowchart in the current project as either Mermaid or D2 source, with a Typst wrapper that embeds the rendered SVG so it compiles into a printable PDF page. Use when the user wants to author a decision tree, branching procedure, or troubleshooting flow that will be rendered alongside or as part of a printed SOP.