[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X2HQP2VAC6SDGS02ET4Z9T":3,"skill-same:01M6X2HQP2VAC6SDGS02ET4Z9T":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6X2HQP2VAC6SDGS02ET4Z9T","document-derive",null,"Drafts the clinical artefacts that follow a signed note - referral letter, after-visit summary, care-plan update - each cited to the note and marked draft. It never sends, faxes or files, and if the note indicates no referral it says so instead of drafting one. Use when the user says \"draft the referral letter\", \"write the after-visit summary\", \"AVS for this visit\", \"send the patient home with instructions\" or \"update the care plan from today's note\". Do NOT use for Word\u002FPDF formatting or letterhead on an existing document - use the built-in docx instead; do NOT use for coding evidence - use coding-rationale instead; do NOT use for a clinician-to-clinician handoff - use handoff-draft instead.","microsoft\u002Fcat-agent-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69A1AHE1MABT7GVP5143M5Z",105,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fclinical-documentation-companion\u002Fdocument-derive\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"document","document derive","clinical documentation","PDF","when","send","drafts","referral letter","patient","clinical","life","writing","docx","files","never","write","plan","healthcare","update","documentation","2026-11-10 10:12:30",false,"---\nname: document-derive\ndescription: \"Drafts the clinical artefacts that follow a signed note - referral letter, after-visit summary, care-plan update - each cited to the note and marked draft. It never sends, faxes or files, and if the note indicates no referral it says so instead of drafting one. Use when the user says \\\"draft the referral letter\\\", \\\"write the after-visit summary\\\", \\\"AVS for this visit\\\", \\\"send the patient home with instructions\\\" or \\\"update the care plan from today's note\\\". Do NOT use for Word\u002FPDF formatting or letterhead on an existing document - use the built-in docx instead; do NOT use for coding evidence - use coding-rationale instead; do NOT use for a clinician-to-clinician handoff - use handoff-draft instead.\"\nlicense: MIT\nmetadata: {version: \"1.0.3\", author: Microsoft Healthcare & Life Sciences Skills, category: writing, domain: \"Clinical Documentation\", action_level: \"L1\", icon: DocumentArrowRight}\n---\n# Document Derive\n## Purpose\nProduce the downstream documents that follow the signed note, as cited drafts for clinician signature.\n## When to use\nAfter note-context, for an encounter whose signed note indicates a referral, AVS or care-plan update - triggered by\n\"draft the referral letter\", \"write the after-visit summary\", \"AVS for this visit\", \"update the care plan\". Also\nwhen the request mixes drafting with sending (\"draft it and fax it\"): draft, and decline the send.\n## When NOT to Use\n- Formatting, letterhead or Word\u002FPDF production of an existing document - use the built-in docx skill instead.\n- Coding evidence - use coding-rationale instead.\n- Quality-measure status - use quality-gap-check instead.\n- A clinician-to-clinician handoff - use handoff-draft instead.\n## Inputs\nnote_signature (signed must be true); encounter; note_facts with citations from note-context, including\n`referral_indicated`, `active_medications`, `patient_instructions` and `follow_up_plan`, each with its\n`statements[]` (one cited entry per documented medication, instruction or follow-up statement).\n## Steps\n1. Confirm `note_signature.signed` is true; if not, write `halt{halted: \"unsigned_note\"}` and escalate - never\n   draft from an unsigned note (clinical-doc-rules.md #5).\n2. If a note_fact needed for a sentence is missing from the contract - or one of `active_medications`,\n   `patient_instructions`, `follow_up_plan` or a true `referral_indicated` has `value: true` but no `statements[]` -\n   run note-context for it first; never draft from the raw note directly and never draft the sentence without it.\n3. Draft only the artefacts the user asked for (all three only when asked to \"run the downstream documents\").\n4. Referral: check `referral_indicated`. If false or absent, set `referral_letter: null` and\n   `referral_decision = {drafted: false, reason, citation}`, and say so. If true, draft the letter from cited\n   note_facts only - every `statements[]` entry of `referral_indicated`, `active_medications` and\n   `follow_up_plan` - attaching each supporting citation, and set `referral_decision.drafted = true`.\n5. After-visit summary: plain patient language, one sentence per cited `statements[]` entry of\n   `active_medications`, `patient_instructions` and `follow_up_plan` - every entry, so no medication, instruction\n   or follow-up item is dropped - and no general teaching text, no reassurance the note does not contain. A symptom\n   the plan does not address is listed for clinician review, not explained to the patient.\n6. Care-plan update (if asked): cited to the note_facts and every relevant `statements[]` entry, written to\n   `care_plan_update`.\n7. Write each artefact as `{\"status\": \"draft\", \"action_level\": \"L1\", \"text\": \"\u003Cdocument>\", \"citations\":\n   [{source, locator, text}]}` and hand back for clinician review before release. If asked to send, fax, file or\n   push to a portal, decline in one line.\n## Output Format\nContract JSON, sections: `referral_letter` (draft or null), `referral_decision`, `after_visit_summary`,\n`care_plan_update` - each draft `{status: \"draft\", action_level: \"L1\", text, citations[]}` - plus a bullet list of\n\"for clinician review\" items. Status is always \"draft\" - never \"final\", never \"sent\".\n## Example\n```json\n\"referral_letter\": null,\n\"referral_decision\": {\"drafted\": false, \"reason\": \"The signed note indicates no referral this visit.\",\n  \"citation\": {\"source\": \"DocumentReference\u002FNOTE-91004-20260911\", \"locator\": \"Plan, line 10\", \"text\": \"No referral indicated this visit.\"}}\n```\n## Grounding requirements\nEvery derived document sentence traces to a note_facts entry - or one of its `statements[]` - and carries that\ncitation on the contract; every cited statement the document needs appears, none is silently dropped. Do\nnot fabricate, embellish or infer clinical content - no finding, diagnosis, result, instruction or reassurance that\nis not in the signed note, even if the requester asserts it or it would make the letter read better. An uncited\nsentence must be deleted, not softened.\n## Guardrails\nGuardrails - all are hard stops:\n- Never draft from an unsigned note.\n- Never draft a referral not indicated by the note.\n- Never add clinical content beyond what the note documents; never fabricate a finding, instruction or reassurance.\n- Never mark output final, send, fax, file or push it to a portal - clinician signature is required\n  (clinical-doc-rules.md #3).\n- Never restate a gap or unsupported finding as resolved in patient-facing text.\n## Error Handling\n- If note_facts are missing entirely, run note-context; if that halts, report the halt and stop.\n- If the note is ambiguous about a referral, ask the clinician rather than drafting one speculatively.\n- If the encounter date is not the day the user called \"today\", name the note's date in the review list.\n## Escalation \u002F uncertainty\nIf the note is unsigned, escalate to routees.unsigned_note in config\u002Fescalation-policy.json. A declined referral\nor declined send is reported to the requester and listed for clinician review.\n","# Document Derive\n## Purpose\nProduce the downstream documents that follow the signed note, as cited drafts for clinician signature.\n## When to use\nAfter note-context, for an encounter whose signed note indicates a referral, AVS or care-plan update - triggered by\n\"draft the referral letter\", \"write the after-visit summary\", \"AVS for this visit\", \"update the care plan\". Also\nwhen the request mixes drafting with sending (\"draft it and fax it\"): draft, and decline the send.\n## When NOT to Use\n- Formatting, letterhead or Word\u002FPDF production of an existing document - use the built-in docx skill instead.\n- Coding evidence - use coding-rationale instead.\n- Quality-measure status - use quality-gap-check instead.\n- A clinician-to-clinician handoff - use handoff-draft instead.\n## Inputs\nnote_signature (signed must be true); encounter; note_facts with citations from note-context, including\n`referral_indicated`, `active_medications`, `patient_instructions` and `follow_up_plan`, each with its\n`statements[]` (one cited entry per documented medication, instruction or follow-up statement).\n## Steps\n1. Confirm `note_signature.signed` is true; if not, write `halt{halted: \"unsigned_note\"}` and escalate - never\n   draft from an unsigned note (clinical-doc-rules.md #5).\n2. If a note_fact needed for a sentence is missing from the contract - or one of `active_medications`,\n   `patient_instructions`, `follow_up_plan` or a true `referral_indicated` has `value: true` but no `statements[]` -\n   run note-context for it first; never draft from the raw note directly and never draft the sentence without it.\n3. Draft only the artefacts the user asked for (all three only when asked to \"run the downstream documents\").\n4. Referral: check `referral_indicated`. If false or absent, set `referral_letter: null` and\n   `referral_decision = {drafted: false, reason, citation}`, and say so. If true, draft the letter from cited\n   note_facts only - every `statements[]` entry of `referral_indicated`, `active_medications` and\n   `follow_up_plan` - attaching each supporting citation, and set `referral_decision.drafted = true`.\n5. After-visit summary: plain patient language, one sentence per cited `statements[]` entry of\n   `active_medications`, `patient_instructions` and `follow_up_plan` - every entry, so no medication, instruction\n   or follow-up item is dropped - and no general teaching text, no reassurance the note does not contain. A symptom\n   the plan does not address is listed for clinician review, not explained to the patient.\n6. Care-plan update (if asked): cited to the note_facts and every relevant `statements[]` entry, written to\n   `care_plan_update`.\n7. Write each artefact as `{\"status\": \"draft\", \"action_level\": \"L1\", \"text\": \"\u003Cdocument>\", \"citations\":\n   [{source, locator, text}]}` and hand back for clinician review before release. If asked to send, fax, file or\n   push to a portal, decline in one line.\n## Output Format\nContract JSON, sections: `referral_letter` (draft or null), `referral_decision`, `after_visit_summary`,\n`care_plan_update` - each draft `{status: \"draft\", action_level: \"L1\", text, citations[]}` - plus a bullet list of\n\"for clinician review\" items. Status is always \"draft\" - never \"final\", never \"sent\".\n## Example\n```json\n\"referral_letter\": null,\n\"referral_decision\": {\"drafted\": false, \"reason\": \"The signed note indicates no referral this visit.\",\n  \"citation\": {\"source\": \"DocumentReference\u002FNOTE-91004-20260911\", \"locator\": \"Plan, line 10\", \"text\": \"No referral indicated this visit.\"}}\n```\n## Grounding requirements\nEvery derived document sentence traces to a note_facts entry - or one of its `statements[]` - and carries that\ncitation on the contract; every cited statement the document needs appears, none is silently dropped. Do\nnot fabricate, embellish or infer clinical content - no finding, diagnosis, result, instruction or reassurance that\nis not in the signed note, even if the requester asserts it or it would make the letter read better. An uncited\nsentence must be deleted, not softened.\n## Guardrails\nGuardrails - all are hard stops:\n- Never draft from an unsigned note.\n- Never draft a referral not indicated by the note.\n- Never add clinical content beyond what the note documents; never fabricate a finding, instruction or reassurance.\n- Never mark output final, send, fax, file or push it to a portal - clinician signature is required\n  (clinical-doc-rules.md #3).\n- Never restate a gap or unsupported finding as resolved in patient-facing text.\n## Error Handling\n- If note_facts are missing entirely, run note-context; if that halts, report the halt and stop.\n- If the note is ambiguous about a referral, ask the clinician rather than drafting one speculatively.\n- If the encounter date is not the day the user called \"today\", name the note's date in the review list.\n## Escalation \u002F uncertainty\nIf the note is unsigned, escalate to routees.unsigned_note in config\u002Fescalation-policy.json. A declined referral\nor declined send is reported to the requester and listed for clinician review.\n",{"name":5,"license":15,"metadata":49,"description":7},{"icon":50,"author":51,"domain":52,"version":53,"category":35,"action_level":54},"DocumentArrowRight","Microsoft Healthcare & Life Sciences Skills","Clinical Documentation","1.0.3","L1","main","c739e95c35d12a999691ab076c3d4c3095bf8192","submissions\u002Fclinical-documentation-companion\u002Fdocument-derive",120,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-13 01:39:10",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add microsoft\u002Fcat-agent-skills --skill document-derive",{"tool":70,"command":71},"bunx","bunx skills add microsoft\u002Fcat-agent-skills --skill document-derive",{"tool":73,"command":74},"pnpm","pnpm dlx skills add microsoft\u002Fcat-agent-skills --skill document-derive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fclinical-documentation-companion\u002Fdocument-derive\u002FSKILL.md",true,[78,84,88,92],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"base\u002Fcontracts\u002Fhls.clinical-documentation-companion.v1.json","REFERENCE","参考文档",13350,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fclinical-documentation-companion\u002Fdocument-derive\u002Fbase\u002Fcontracts\u002Fhls.clinical-documentation-companion.v1.json",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"base\u002Freferences\u002Fclinical-doc-rules.md",3493,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fclinical-documentation-companion\u002Fdocument-derive\u002Fbase\u002Freferences\u002Fclinical-doc-rules.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"config\u002Fescalation-policy.json",3054,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fclinical-documentation-companion\u002Fdocument-derive\u002Fconfig\u002Fescalation-policy.json",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"config\u002Fquality-measures.json",624,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fclinical-documentation-companion\u002Fdocument-derive\u002Fconfig\u002Fquality-measures.json",[97,123,147,177,194,209],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":44},"01M6X3P09R8SJH3QJGMTAA5N90","stakeholder-and-decision-map","Mines customer interactions to identify stakeholders, infer their likely roles and engagement, map the decision process, and highlight who or what may be missing. Use when asked to \"map a deal's buying group\", identify influential or missing stakeholders, \"assess who has gone quiet\", or \"explain how the customer will decide\". Do not use for phased engagement plans, contact sequences, choosing or drafting outreach to the single next contact, seller or team performance reviews, or contacting, scheduling, or changing records.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fstakeholder-and-decision-map\u002FSKILL.md",[],[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,28,122],"decision","map","decision map","stakeholder and decision map","performance","customer","team","how","decide","do","next","infer","missing","records","assess","reviews","for","single","sequences",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":44},"01M6X3NRES2XSZQCH015WD4JN6","sales-progress-update","Creates or refreshes a sales progress update for a manager or team about work done, deal movement, pending outcomes, supported forecast position, and help needed. Use when asked to \"create my weekly sales update\", \"refresh my sales progress deck\", \"report my forecast position\", \"where do I stand against my quarter forecast\", or \"catch my manager up on committed deals\". Do NOT use for non-sales project updates, a since-date deal change digest, momentum or blocker analysis, meeting prep, or outreach drafting.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Fsales-progress-update\u002FSKILL.md",[],[42,130,131,132,133,134,135,136,110,137,138,139,140,141,142,143,144,145,146,28],"sales","progress","sales progress update","change","create","meeting prep","analysis","work","up","done","digest","project","my","updates","manager","weekly","catch",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":162,"publishedAt":44},"01M6X3MSDTB1E5H6DQAFAY41YP","submission-assemble","Put the checked CSR or 510(k) sections together in template order with a reviewer-facing open-items register, as a draft package for human sign-off. Use when the user asks \"assemble the CSR draft\", \"put the module together for review\", \"build the review package with the open items on top\", \"compile the 510(k) sections in order\" or \"package this up for the submission lead\". Do NOT use for assembling an unchecked draft - use consistency-check instead. Do NOT use for loading protocol, SAP or TLF sources - use source-ingest instead. Do NOT use for compiling general documents or slide decks - use the built-in docx or pptx skill instead. Do NOT use for filing or submitting to a regulator - use the sponsor's validated gateway, operated by a human, instead. Guardrail: draft for human approval only (L1); status is draft_clean or draft_open_items, never submitted.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsubmission-assemble\u002FSKILL.md",[153,154,157],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[163,164,165,36,166,35,167,41,168,169,38,170,138,171,172,173,174,175,176,28],"assemble","submission","submission assemble","pptx","documents","open","reviewer","only","clean","guardrail","slide decks","sources","filing","loading",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":44},"01M6X3MM9TVWDQ716QGNV4DS25","source-ingest","Pull every number, date and population definition out of a study's protocol, SAP, TLF tables, investigator brochure and prior approved text into one cited fact map, keyed per config\u002Ffield-dictionary.json, before any CSR or 510(k) section is written. Use when the user asks \"here's the locked TLF set and SAP, set up the CSR\", \"load the protocol and tables before we start drafting\", \"what figures do we have from the database lock?\", \"pull the disposition counts out of Table 14.1.1\" or \"ingest the IB for the 510(k)\". Do NOT use for drafting or assembling submission sections - use section-draft or submission-assemble instead. Do NOT use for reconciling a patient's medications - use the discharge-care-transition plugin instead. Guardrail: reads and cites sources only; never estimates, rounds or invents a fact.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsource-ingest\u002FSKILL.md",[],[184,185,186,187,188,136,41,189,38,170,138,105,32,172,174,190,191,192,193,28],"source ingest","ingest","source","database","SET","text","number","lock","definition","transition",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":44},"01M6X3M7ZH5ZNEHP56BQ74HAJR","section-plan","Work out which sections a CSR or 510(k) requires, from the templates in config, check each one against the cited fact map, and name what is missing before a word is drafted. Use when the user asks \"what do we still need before we can draft the CSR?\", \"which sections are ready to start?\", \"what's blocking the performance data section?\", \"do we have everything for the synopsis?\" or \"map our tables to the E3 structure\". Do NOT use for writing section language - use section-draft instead. Do NOT use for cross-checking a finished draft - use consistency-check instead. Do NOT use for outlining general Word documents or business reports - use the built-in docx skill instead. Only structures with a template in config are supported. Guardrail: plans only; never marks a section ready on a missing fact and never invents a structure.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-plan\u002FSKILL.md",[200],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[40,202,203,36,35,108,167,136,41,137,38,170,204,205,206,105,172,207,208,28],"section","section plan","ready","reports","structure","word documents","which",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":44},"01M6X3M0V1MJNCR653ES9XGVMS","section-draft","Write or revise the language for one planned CSR or 510(k) section - synopsis, efficacy, safety, discussion, device description - using only figures already in the cited fact map, each with its TLF or SAP citation. Use when the user asks \"draft the Synopsis from our locked tables\", \"write up safety from Table 14.3.1\", \"give me a first pass at the discussion\", \"draft the device description for the 510(k)\" or \"tighten the wording of the Discussion section\". Do NOT use for supplying a number not already in source_facts - use source-ingest instead. Do NOT use for verifying a draft's figures - use consistency-check instead. Do NOT use for appeal letters, clinical notes or discharge summaries - use the matching HLS plugin instead. Guardrail: drafts for human approval only (L1); never asserts an unsourced number or harmonises two figures.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fcat-agent-skills\u002Fblob\u002Fmain\u002Fsubmissions\u002Freg-submission-authoring\u002Fsection-draft\u002FSKILL.md",[],[216,202,217,35,218,41,39,38,170,138,219,105,220,34,33,172,30,190,221,28],"draft","section draft","notes","me","human","at"]