{"id":44226,"plugin_id":"plugin_asdk_app_6a958f23ec408191a845944d93e24925","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:15:25.446Z","digest":"a51234017ef395156edb9cbc3d5705da810152519523093731446cb31a066901","against":null,"payload":{"description":"Hand a document drafted in the conversation to the office's Word template: clean Markdown with a stable heading plan, tables, citations and visible gaps, plus the two lines the person needs to paste it. Use only for a text that was not written with draft_deliverable, which the dossier page exports to Word itself. Trigger phrases: \"mets-le en forme pour Word\", \"prepare pour le gabarit\", \"export pour Word\", \"paste into Word\".","included_files":[],"name":"handoff-to-word","skill_md_contents":"---\nname: handoff-to-word\ndescription: Hand a document drafted in the conversation to the office's Word template: clean Markdown with a stable heading plan, tables, citations and visible gaps, plus the two lines the person needs to paste it. Use only for a text that was not written with draft_deliverable, which the dossier page exports to Word itself. Trigger phrases: \"mets-le en forme pour Word\", \"prepare pour le gabarit\", \"export pour Word\", \"paste into Word\".\n---\n\n# Handoff to Word\n\nUse this skill when a document was drafted in the conversation (a terrain chapter, a\nnote) and the office wants it in its own Word template. A document written with\n`draft_deliverable` and `write_section` does not need it: the dossier page exports it to\nWord under Livrables, headings and sources included; tell the user so.\n\nDo not use it to write the document: it formats one that exists.\n\n## What to produce\n\n1. The document as Markdown with a stable plan: `#` for the title, `##` for chapters\n   numbered as the office numbers them, `###` at most. No deeper level: Word templates\n   rarely style a fourth.\n2. Tables as Markdown tables with a header row; one table per subject, no merged cells.\n3. Provenance marks kept exactly as the source skill wrote them: `(#xxxxxx)` for dossier\n   entries, `[CODE section, p. N]` for clauses, `(fait: topic.key)` for site facts. They\n   are what the reviewer checks; a Word document without them is prose.\n4. Gaps kept as `[A etablir : ...]`, `[A confirmer : ...]` or `[A convenir : ...]`, on\n   their own line when they replace a paragraph, so they show up in a search.\n5. A final section **Sources** listing every clause cited with its edition and every\n   attachment cited with its page.\n\n## Then tell the user, in two lines\n\n- How to paste: in Word, paste as text, then apply the template's heading styles to the\n  `#` levels (or use the office's Markdown import when it has one).\n- That the dossier page produces the verification note as a PDF, hashed and\n  timestamped, and that the two documents should agree.\n\n## Rules\n\n- Change nothing in the content: no rewording, no reordering, no gap filled.\n- Keep the closing sentence of the source document (\"Document prepare par un agent...\").\n- The office may have its own `handoff-to-word` skill (`list_skills`), for instance\n  with its heading numbering or its table style: it replaces this one.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}