ur-agent 1.23.2 → 1.24.0

package/marketplace-plugins/word/README.md

@@ -0,0 +1,37 @@
+# word
+
+Create, convert, review, and edit Microsoft Word documents from any UR session.
+Backed by the **Office Word MCP server** (python-docx, ~54 tools), with a
+`pandoc` / `python-docx` fallback so the commands still work headless.
+
+## Commands
+
+| Command | Argument | What it does |
+| --- | --- | --- |
+| `/docx-new` | `<brief \| outline.md>` | Create a styled document from a brief or outline. |
+| `/docx-from-md` | `<file.md> [out.docx]` | Convert Markdown to a styled `.docx`. |
+| `/docx-review` | `<file.docx>` | Report structure, styling, and accessibility issues with a verdict. |
+| `/docx-edit` | `<file.docx> — <change>` | Apply targeted edits while preserving styles. |
+
+A bundled `document-craft` skill defines the styling and accessibility
+conventions all commands follow.
+
+## Setup
+
+```sh
+/plugin install word@ur-plugins-official
+```
+
+The MCP server runs via `uvx`, so install **uv** once
+(`curl -LsSf https://astral.sh/uv/install.sh | sh`). UR launches
+`uvx --from office-word-mcp-server word_mcp_server` on demand — no manual clone.
+Optionally set **DOCX_DIR** as the default output folder.
+
+Fallbacks use `pandoc` (Markdown → docx) and `python-docx`
+(`pip install python-docx`); install either if you want the commands to work
+without `uvx`.
+
+## Security
+
+The server operates on local files only. Edits preserve existing styles, and
+in-place overwrites can keep a backup on request.

package/marketplace-plugins/word/commands/docx-edit.md

@@ -0,0 +1,18 @@
+---
+description: Apply targeted edits to a Word document — find/replace, add sections, restyle.
+argument-hint: "<path/to/file.docx> — <what to change>"
+---
+
+Edit the `.docx` named in `$ARGUMENTS`. Split the argument into the file path and
+the change instruction (separated by `—`, `:`, or a newline). If either is
+missing, ask for it and stop.
+
+1. Read the document so edits respect its existing structure and styles.
+2. Apply only the requested change: find/replace text, insert or remove a
+   heading/section, restyle a range, update a table, refresh the TOC. Preserve
+   every unrelated paragraph and its style exactly.
+3. Save in place. Before overwriting, note that a copy can be kept on request.
+
+Prefer the `word` MCP tools (`find_and_replace`, `add_heading`, `format_text`,
+...). If unavailable, fall back to `python-docx`. Report a concise diff of what
+changed — sections touched, replacements made — not the whole document.

package/marketplace-plugins/word/commands/docx-from-md.md

@@ -0,0 +1,19 @@
+---
+description: Convert a Markdown file into a styled Word document.
+argument-hint: "<path/to/file.md> [output.docx]"
+---
+
+Convert a Markdown file to `.docx`.
+
+1. Read the source Markdown at the first argument. If missing, ask for a path
+   and stop.
+2. Map structure to Word styles: `#`→Title or Heading 1, `##`/`###`→Heading 2/3,
+   lists→list styles, fenced code→a monospace style, tables→Word tables, images
+   →embedded with the alt text preserved.
+3. Write to the second argument if given, else the same basename with a `.docx`
+   extension in `${user_config.DOCX_DIR}` or the current directory.
+
+Prefer the `word` MCP tools. If unavailable, use `pandoc -o <out>.docx <in>.md`
+when pandoc is installed; otherwise fall back to `python-docx` for headings,
+paragraphs, lists, and tables. Report the path and note anything that did not
+map cleanly.

package/marketplace-plugins/word/commands/docx-new.md

@@ -0,0 +1,22 @@
+---
+description: Create a new Word document from a brief or an outline.
+argument-hint: "<topic / brief> or <path/to/outline.md>"
+---
+
+Create a `.docx` from `$ARGUMENTS`. If empty, ask for a topic or outline and stop.
+
+1. Gather the brief: if `$ARGUMENTS` is a path to a file, read it as the outline;
+   otherwise treat the text as the brief and propose a structure first.
+2. Plan the document: a title, optional subtitle/author, a logical heading
+   hierarchy, and the sections to write. Confirm a long structure before writing
+   if it is non-trivial.
+3. Build the document using real Word styles — `Title`, `Heading 1/2/3`, body —
+   never manual bold/size as a substitute for styles. Add a table of contents
+   field if there are three or more H1s.
+4. Save to `${user_config.DOCX_DIR}` if set, else the current directory, with a
+   slugged filename.
+
+Prefer the `word` MCP tools (`create_document`, `add_heading`, `add_paragraph`,
+`add_table`, ...). If the server is unavailable, fall back to `python-docx` via
+Bash. Apply the `document-craft` conventions. Report the path and the final
+outline.

package/marketplace-plugins/word/commands/docx-review.md

@@ -0,0 +1,29 @@
+---
+description: Review a Word document's structure, styling, and accessibility.
+argument-hint: "<path/to/file.docx>"
+---
+
+Review the `.docx` at `$ARGUMENTS`. If empty, ask for a path and stop.
+
+Read the document and report, skipping any section with no findings:
+
+### Structure
+Heading hierarchy sanity (no skipped levels, one Title), section/page breaks,
+presence and correctness of a table of contents.
+
+### Styling
+Manual formatting used where a style belongs, inconsistent fonts or sizes,
+direct color use, hard line breaks faking spacing.
+
+### Accessibility
+Images without alt text, tables without header rows, low-contrast text, links
+with bare URLs instead of descriptive text.
+
+### TL;DR
+End with exactly one of:
+- `TL;DR: Clean.`
+- `TL;DR: Minor fixes.`
+- `TL;DR: Needs structural work.`
+
+Prefer the `word` MCP tools to read the document; otherwise inspect it with
+`python-docx`. Do not modify the file — this command only reports.

package/marketplace-plugins/word/skills/document-craft/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: Document Craft (Word)
+description: Conventions for producing professional Microsoft Word documents — styles over manual formatting, heading hierarchy, tables of contents, templates, track changes, tables, and accessibility. Use when creating, converting, reviewing, or editing .docx files.
+version: 0.1.0
+---
+
+# Document Craft (Word)
+
+A Word document is a structured object, not formatted text. Edit the structure;
+let styles carry the look.
+
+## Styles over manual formatting
+
+- Use `Title`, `Heading 1/2/3`, `Normal`, `Quote`, and list styles. Never fake a
+  heading with bold + larger font — it breaks navigation, the TOC, and
+  accessibility.
+- Change appearance by editing the style once, not each paragraph.
+- One font family for body, one for headings. Avoid per-paragraph color and size.
+
+## Heading hierarchy
+
+- Exactly one `Title`. Do not skip levels (no H1 → H3).
+- Headings are an outline: a reader should grasp the document from them alone.
+
+## Table of contents
+
+- Insert a TOC **field**, not a typed list, so it updates with the headings.
+- Add one when the document has three or more H1 sections.
+
+## Templates
+
+- Start from a `.dotx` template for repeated document types to inherit styles,
+  margins, and a title block. Keep brand styling in the template, not the content.
+
+## Track changes and comments
+
+- For review cycles, enable track changes so edits are visible and reversible.
+- Use comments for questions and suggestions; resolve them before finalizing.
+
+## Tables
+
+- Mark the first row as a header row (repeats across pages, aids accessibility).
+- Use table styles for banding; avoid manual cell shading per row.
+
+## Accessibility
+
+- Every image needs alt text.
+- Links use descriptive text, not a bare URL.
+- Maintain reading order and sufficient contrast; do not encode meaning in color
+  alone.
+
+## Page setup
+
+- Set margins, headers/footers, and page numbers via section settings, not blank
+  paragraphs and tabs.
+
+## Guardrails
+
+- Preserve existing styles when editing; do not restyle untouched content.
+- Offer to keep a copy before overwriting a document in place.
+- Do not flatten styled content to plain paragraphs during conversion.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ur-agent",
-  "version": "1.23.2",
+  "version": "1.24.0",
   "description": "UR — autonomous engineering workflow engine (plan, execute, test, verify, document, benchmark, reproduce)",
   "type": "module",
   "packageManager": "bun@1.3.14",
@@ -30,6 +30,7 @@
     "documentation",
     "extensions",
     "examples",
+    "marketplace-plugins",
     "CHANGELOG.md",
     "QUALITY.md",
     "README.md",