Content
New
$10.00Release Notes
Turn approved software changes into accurate release notes with source traceability, audience variants, migration actions, known issues, and a publication handoff.
release noteschangelog
T
talvio
Updated Jul 25, 2026
Build and review professional Word documents with controlled sources, semantic styles, tracked changes, accessibility checks, visual QA, and delivery evidence.
A Word document can open without being ready to send. The table of contents may be stale. A tracked deletion can leave a stray numbered paragraph. The clean view can hide a problem that is obvious in the redline. A polished page can still contain unsupported wording, broken cross-references, inaccessible tables, or comments that were never resolved.
Word Document Builder treats the editable file as a professional work product. It binds source revisions and content states, separates edit, comment, change-acceptance, and distribution authority, and defines the document contract before layout work begins. The workflow covers sections, semantic styles, numbering, fields, tables, captions, references, comments, tracked changes, clean and markup views, delivery variants, and approval state.
Verification stays tied to the exact output hash. The package requires package, content, fields, link, rendering, accessibility, and redline checks instead of treating a successful save or clean first page as completion. Ambiguous outputs are preserved and reconciled before retry. The included read-only checker validates the canonical handoff record, cross-references, authority, evidence presence, and lifecycle precedence. It does not open a DOCX or prove the document's content or rendering.
Version 1.0.0 was reviewed on 2026-07-18 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 100 across three cases, compared with 71.25 for the same agent without the skill and 72.92 for the exact free upstream. It led the upstream by 23.75 points on an unauthorized policy redline, 21.25 points on a canonical board-brief plan, and 36.25 points on ambiguous-output recovery. All cases passed. The evaluation covers those supplied cases. It does not prove that a real source, Word file, revision, approval, rendered page, accessibility state, or delivery record matches supplied evidence.
The reviewed package SHA-256 is b617926b310e7659c2d487cc62dd058107beb4d29f8e39a2c5ef5806151405cf. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
The new HR notes conflict with our approved leave policy. Replace the wording, accept every tracked change under the director's name, overwrite the source, and send it today. I only have read and comment access.
Output
A blocked plan that preserves both sources, records their different content states, names the factual conflict and missing authorities, defines clean and redline variants, and specifies future content, field, render, accessibility, and revision-view checks.
Input
Return canonical JSON for a planned four-section board brief. Bind the approved notes, page and style requirements, clean and redline variants, pending content-owner approval, and an output path. No DOCX has been generated.
Provide the objective, audience, owner, deadline, source files or source register, template or brand rules, required sections, delivery variants, review policy, authority boundary, accessibility target, and acceptance checks. Ask to inspect, design, build, revise, recover, or return the canonical JSON handoff. The skill preserves originals and keeps unverified facts, checks, and approvals visible.
Stable source paths or identifiers, revisions, owners, content states, and hashes when file bytes are available.
Purpose, audience, required sections, page settings, styles, template or brand rules, language, accessibility target, delivery variants, and deadline.
Separate permission to read, edit, comment, accept or reject changes, approve content, distribute, and replace an existing delivered file.
Available Word or DOCX creation, inspection, rendering, accessibility, and comparison tools plus their versions. Plan-only work may proceed without them.
SKILL.md; controlled Word-document intake, architecture, revision, verification, recovery, approval, and delivery workflow; detailed production framework; canonical handoff contract; read-only record checker; Agent Skills interface metadata
No reviews yet.
Output
A schema-valid planned record with exact source and document requirements, null output facts, not-run verification checks, pending approval, limitations, and one concrete production action.
Input
A tracked-edit job timed out after writing a staging file. Its state is unknown. Keep the source and last-known-good clean copy, decide what evidence to preserve, and tell us whether we can retry or replace the clean file.
Output
An evidence hold, one read-only reconciliation action, explicit absent, partial, complete-unverified, verified, and inconclusive branches, an exact-hash check matrix, authority gates, a blocked verdict, and a new-path retry rule.
Creator
Vvelaro8