{"id":21258,"plugin_id":"plugins_6aad979cf8348191812bd2ac0cce6181","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:52.318Z","digest":"3d6feb2bea1d2f340d08447bbf82a2e59b98484ee5bee847dd0e1bdfde3d7939","against":null,"payload":{"description":"Plan and create polished professional documents and artifact suites such as strategy papers, business plans, proposals, reports, briefs, SOPs, presentations, spreadsheets, and decision memos. Use when the user needs a complete business artifact and the correct file-specific skill should be selected and coordinated.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":246}],"name":"create-professional-documents","skill_md_contents":"---\nname: create-professional-documents\ndescription: Plan and create polished professional documents and artifact suites such as strategy papers, business plans, proposals, reports, briefs, SOPs, presentations, spreadsheets, and decision memos. Use when the user needs a complete business artifact and the correct file-specific skill should be selected and coordinated.\n---\n# Create Professional Documents\n1. Define document purpose, audience, decision, format, language, brand, source material, constraints, and acceptance criteria.\n2. Select the correct artifact and invoke available document, presentation, spreadsheet, or PDF skills when producing those file types.\n3. Build an evidence-backed outline and assign each section a communication job.\n4. Draft with consistent terminology, hierarchy, tables/visuals only when helpful, citations, and explicit assumptions.\n5. Verify factual accuracy, completeness, tone, accessibility, layout, links, and requested file behavior.\n6. Deliver final artifact, source/assumption note, and concise usage guidance. Do not claim a file was rendered or verified unless it was.\n\n## Implementation-package boundary\n\nFor a complex multi-document developer specification package, route architecture, authority, precedence, and readiness to `$architect-implementation-documentation`. This skill may render or format approved source content, but must establish content structure and correctness before layout work.\n\nCarry artifact ID, version, status, owner, date, sources, usage class, relationships, and downstream dependencies into controlled outputs. A clean, premium, or complete-looking document is not thereby `FINAL` or implementation-ready.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}